Button functionality

ABSTRACT

Button functionalities for user interfaces, e.g., for use with a portable multifunction device, are disclosed. Exemplary button functionalities are described for an electronic device with a display, a rotatable and depressible input mechanism, and/or a button. Different device features may be accessed, depending on whether the rotatable and depressible input mechanism or the button is activated, and further depending on whether the activation represents a single press, a double press, or an extended press on the rotatable and depressible input mechanism or the button.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/378,451, entitled “BUTTON FUNCTIONALITY,” filed Jul. 16, 2021, whichis a continuation of U.S. patent application Ser. No. 16/384,726, nowU.S. Pat. No. 11,068,083, entitled “BUTTON FUNCTIONALITY,” filed Apr.15, 2019, which is a continuation of U.S. patent application Ser. No.16/055,489, now U.S. Pat. No. 10,281,999, entitled “BUTTONFUNCTIONALITY,” filed Aug. 6, 2018, which is a continuation of U.S.patent application Ser. No. 14/641,252, now U.S. Pat. No. 10,082,892,entitled “BUTTON FUNCTIONALITY,” filed Mar. 6, 2015, which claimspriority to U.S. Provisional Patent Application No. 62/044,922, entitled“BUTTON FUNCTIONALITY,” filed Sep. 2, 2014, the contents of each ofwhich are hereby incorporated by reference in their entireties.

This application relates to the following applications: InternationalPatent Application Serial No. PCT/US2013/040087, entitled “Device,Method, and Graphical User Interface for Moving a User Interface ObjectBased on an Intensity of a Press Input,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040072, entitled“Device, Method, and Graphical User Interface for Providing Feedback forChanging Activation States of a User Interface Object,” filed May 8,2013; International Patent Application Serial No. PCT/US2013/040070,entitled “Device, Method, and Graphical User Interface for ProvidingTactile Feedback for Operations Performed in a User Interface,” filedMay 8, 2013; International Patent Application Serial No.PCT/US2013/040067, entitled “Device, Method, and Graphical UserInterface for Facilitating User Interaction with Controls in a UserInterface,” filed May 8, 2013; International Patent Application SerialNo. PCT/US2013/040061, entitled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013; International Patent Application SerialNo. PCT/US2013/040058, entitled “Device, Method, and Graphical UserInterface for Displaying Additional Information in Response to a UserContact,” filed May 8, 2013; International Patent Application Serial No.PCT/US2013/040056, entitled “Device, Method, and Graphical UserInterface for Scrolling Nested Regions,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040054, entitled“Device, Method, and Graphical User Interface for Manipulating FramedGraphical Objects,” filed May 8, 2013; International Patent ApplicationSerial No. PCT/US2013/069489, entitled “Device, Method, and GraphicalUser Interface for Switching Between User Interfaces,” filed Nov. 11,2013; International Patent Application Serial No. PCT/US2013/069486,entitled “Device, Method, and Graphical User Interface for DeterminingWhether to Scroll or Select Content,” filed Nov. 11, 2013; InternationalPatent Application Serial No. PCT/US2013/069484, entitled “Device,Method, and Graphical User Interface for Moving a Cursor According to aChange in an Appearance of a Control Icon with SimulatedThree-Dimensional Characteristics,” filed Nov. 11, 2013; InternationalPatent Application Serial No. PCT/US2013/069483, entitled “Device,Method, and Graphical User Interface for Transitioning Between TouchInput to Display Output Relationships,” filed Nov. 11, 2013;International Patent Application Serial No. PCT/US2013/069479, entitled“Device, Method, and Graphical User Interface for Forgoing Generation ofTactile Output for a Multi-Contact Gesture,” filed Nov. 11, 2013;International Patent Application Serial No. PCT/US2013/069472, entitled“Device, Method, and Graphical User Interface for Navigating UserInterface Hierarchies,” filed Nov. 11, 2013; International PatentApplication Serial No. PCT/US2013/040108, entitled “Device, Method, andGraphical User Interface for Moving and Dropping a User InterfaceObject,” filed May 8, 2013; International Patent Application Serial No.PCT/US2013/040101, entitled “Device, Method, and Graphical UserInterface for Selecting User Interface Objects,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040098, entitled“Device, Method, and Graphical User Interface for Displaying ContentAssociated with a Corresponding Affordance,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040093, entitled“Device, Method, and Graphical User Interface for Transitioning BetweenDisplay States in Response to a Gesture,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040053, entitled“Device, Method, and Graphical User Interface for Selecting Objectwithin a Group of Objects,” filed May 8, 2013; U.S. Patent ApplicationSer. No. 61/778,211, entitled “Device, Method, and Graphical UserInterface for Facilitating User Interaction with Controls in a UserInterface,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,191, entitled “Device, Method, and Graphical User Interface forDisplaying User Interface Objects Corresponding to an Application,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,171,entitled “Device, Method, and Graphical User Interface for DisplayingAdditional Information in Response to a User Contact,” filed Mar. 12,2013; U.S. Patent Application Ser. No. 61/778,179, entitled “Device,Method and Graphical User Interface for Scrolling Nested Regions,” filedMar. 12, 2013; U.S. Patent Application Ser. No. 61/778,156, entitled“Device, Method, and Graphical User Interface for Manipulating FramedGraphical Objects,” filed Mar. 12, 2013; U.S. Patent Application Ser.No. 61/778,125, entitled “Device, Method, And Graphical User Interfacefor Navigating User Interface Hierarchies,” filed Mar. 12, 2013; U.S.Patent Application Ser. No. 61/778,092, entitled “Device, Method, andGraphical User Interface for Selecting Object Within a Group ofObjects,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,418, entitled “Device, Method, and Graphical User Interface forSwitching Between User Interfaces,” filed Mar. 13, 2013; U.S. PatentApplication Ser. No. 61/778,416, entitled “Device, Method, and GraphicalUser Interface for Determining Whether to Scroll or Select Content,”filed Mar. 13, 2013; U.S. Patent Application Ser. No. 61/747,278,entitled “Device, Method, and Graphical User Interface for ManipulatingUser Interface Objects with Visual and/or Haptic Feedback,” filed Dec.29, 2012; U.S. Patent Application Ser. No. 61/778,414, entitled “Device,Method, and Graphical User Interface for Moving and Dropping a UserInterface Object,” filed Mar. 13, 2013; U.S. Patent Application Ser. No.61/778,413, entitled “Device, Method, and Graphical User Interface forSelecting User Interface Objects,” filed Mar. 13, 2013; U.S. PatentApplication Ser. No. 61/778,412, entitled “Device, Method, and GraphicalUser Interface for Displaying Content Associated with a CorrespondingAffordance,” filed Mar. 13, 2013; U.S. Patent Application Ser. No.61/778,373, entitled “Device, Method, and Graphical User Interface forManaging Activation of a Control Based on Contact Intensity,” filed Mar.12, 2013; U.S. Patent Application Ser. No. 61/778,265, entitled “Device,Method, and Graphical User Interface for Transitioning Between DisplayStates in Response to a Gesture,” filed Mar. 12, 2013; U.S. PatentApplication Ser. No. 61/778,367, entitled “Device, Method, and GraphicalUser Interface for Moving a User Interface Object Based on an Intensityof a Press Input,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,363, entitled “Device, Method, and Graphical User Interface forTransitioning Between Touch Input to Display Output Relationships,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,287,entitled “Device, Method, and Graphical User Interface for ProvidingFeedback for Changing Activation States of a User Interface Object,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,284,entitled “Device, Method, and Graphical User Interface for ProvidingTactile Feedback for Operations Performed in a User Interface,” filedMar. 12, 2013; U.S. Patent Application Ser. No. 61/778,239, entitled“Device, Method, and Graphical User Interface for Forgoing Generation ofTactile Output for a Multi-Contact Gesture,” filed Mar. 12, 2013; U.S.Patent Application Ser. No. 61/688,227, entitled “Device, Method, andGraphical User Interface for Manipulating User Interface Objects withVisual and/or Haptic Feedback,” filed May 9, 2012; U.S. ProvisionalPatent Application Ser. No. 61/645,033, filed on May 9, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. ProvisionalPatent Application Ser. No. 61/665,603, filed on Jun. 28, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. ProvisionalPatent Application Ser. No. 61/681,098, filed on Aug. 8, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. Utilityapplication Ser. No. 12/987,982, filed Jan. 10, 2011, entitled“Intelligent Automated Assistant;” and U.S. Provisional PatentApplication Ser. No. 62/004,886, filed May 29, 2014, entitled “UserInterface for Payments”. The content of these applications is herebyincorporated by reference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to button functionalities for user interfaces.

BACKGROUND

Users rely on portable multifunction devices for a variety ofoperations, such as communicating with friends, accessing and displayinginformation, and running software applications. A user may wish toinvoke user interfaces for these operations in a quick and convenientway. It is desirable for the user interface for invoking operations tobe intuitive and comprehensible to a user. As electronics packagingtechniques improve, smaller and more portable devices are made, whichfurther challenges computer user interface designers by reducing theavailable real estate to display affordances, user interface objects,and icons for accessing various user interfaces.

SUMMARY

It is desirable to provide user access to numerous user interfaces in away that is intuitive and comprehensible to a user. Therefore,multifunctional button functionalities for portable multifunctiondevices are increasingly desirable for providing access to userinterfaces.

In some embodiments, a method of providing button functionalities foruser interfaces comprises: at an electronic device with a display and arotatable and depressible input mechanism: receiving data representingan activation of the rotatable and depressible input mechanism, theactivation having an associated activation duration; determining whetherthe activation duration exceeds a predetermined threshold; determining astate of an active application; and in accordance with a determinationthat the activation duration exceeds the predetermined threshold, and inaccordance with a determination of the state of the active application:performing an action.

In some embodiments, a method of providing button functionalities foruser interfaces comprises: at an electronic device with a display and arotatable and depressible input mechanism: receiving data representingan activation of the rotatable and depressible input mechanism, theactivation having an associated activation duration; determining whetherthe activation duration exceeds a predetermined threshold; in accordancewith a determination that the activation duration does not exceed thepredetermined threshold: displaying a first user interface screen on thedisplay, the first user interface screen including a plurality ofaffordances, the plurality of affordances comprising an affordancerepresenting an application; while the first user interface screen isdisplayed, receiving second data representing a second activation of therotatable and depressible input mechanism, the second activation havingan associated second activation duration; determining whether the secondactivation duration exceeds a second predetermined threshold; and inaccordance with a determination that the second activation duration doesnot exceed the second predetermined threshold: substituting the displayof the first user interface screen with a display of a second userinterface screen, the second user interface screen including a clockface.

In some embodiments, a method of providing button functionalities foruser interfaces comprises: at an electronic device with a display and arotatable and depressible input mechanism: receiving first datarepresenting a first activation of the rotatable and depressible inputmechanism and a second activation of the rotatable and depressible inputmechanism, the first and the second activations having an associatedinterval between the first and the second activations; in response toreceiving the first data, determining whether the interval between thefirst and the second activations exceeds a predetermined threshold; andin accordance with a determination that the interval does not exceed thepredetermined threshold: invoking a previously invoked application.

In some embodiments, a method of providing button functionalities foruser interfaces comprises: at an electronic device with atouch-sensitive display, a button, and a rotatable and depressible inputmechanism: receiving first data representing an activation of thebutton, the activation having an associated activation duration;determining whether the activation duration exceeds a predeterminedthreshold; and in accordance with a determination that the activationduration does not exceed the predetermined threshold: displaying a userinterface screen, the user interface screen including at least a firstaffordance indicating a contact from a designated list of one or morecontacts, wherein the designated list is a subset of a full list ofcontacts on the electronic device.

In some embodiments, a method of providing button functionalities foruser interfaces comprises: at an electronic device with atouch-sensitive display, a button, and a rotatable and depressible inputmechanism: receiving first data representing a first activation of thebutton and a second activation of the button, the first and the secondactivations having an associated interval between the first and thesecond activations; determining whether the interval between the firstand the second activations exceeds a predetermined threshold; and inaccordance with a determination that the interval does not exceed thepredetermined threshold: invoking a payments application.

In some embodiments, a method of providing button functionalities foruser interfaces comprises: at an electronic device with a display, abutton, and a rotatable and depressible input mechanism: receiving datarepresenting an activation of the button and an activation of therotatable and depressible input mechanism, wherein the activation of thebutton has a first associated activation duration, wherein theactivation of the rotatable and depressible input mechanism has a secondassociated activation duration and overlaps with the activation of thebutton for an overlap interval, and wherein the activation of the buttonand the activation of the rotatable and depressible input mechanism arereceived substantially simultaneously; determining whether the data meetpredetermined criteria; and in accordance with a determination that thedata meet the predetermined criteria: rebooting the electronic device.

In some embodiments, a method of providing button functionalities foruser interfaces comprises: at an electronic device with a display, arotatable and depressible input mechanism and a button: receiving firstdata representing an activation of the rotatable and depressible inputmechanism; determining whether the activation represents: a single pressof the rotatable and depressible input mechanism, the single presshaving an associated press duration; a double press of the rotatable anddepressible input mechanism, the double press having an associatedinterval between a first press of the rotatable and depressible inputmechanism and a second press of the rotatable and depressible inputmechanism, the first and the second presses of the rotatable anddepressible input mechanism each having an associated press duration; oran extended press of the rotatable and depressible input mechanism, theextended press having an associated press duration; and in accordancewith a determination that the activation represents a single press ofthe rotatable and depressible input mechanism: displaying a first userinterface screen on the display, the first user interface screenincluding a plurality of affordances, the plurality of affordancescomprising an affordance representing an application; in accordance witha determination that the activation represents a double press of therotatable and depressible input mechanism: invoking a previously invokedapplication; and in accordance with a determination that the activationrepresents an extended press of the rotatable and depressible inputmechanism: determining a state of an active application; and inaccordance with a determination of the state of the active application:performing an action.

In some embodiments, a method of providing button functionalities foruser interfaces comprises: at an electronic device with a display, arotatable and depressible input mechanism and a button: receiving firstdata representing an activation of the button; determining whether theactivation represents: a single press of the button, the single presshaving an associated press duration; a double press of the button, thedouble press having an associated interval between a first consecutivepress and a second consecutive press, the first and second consecutivepresses each having an associated press duration; or an extended pressof the button, the extended press having an associated press duration;and in accordance with a determination that the activation represents asingle press of the button: displaying a first user interface screen,the first user interface screen including at least a first affordanceindicating a contact from a designated list of one or more contacts,wherein the designated list is a subset of a full list of contacts onthe electronic device; in accordance with a determination that theactivation represents a double press of the button: invoking a paymentsapplication; and in accordance with a determination that the activationrepresents an extended press of the button: displaying a second userinterface screen, the second user interface screen comprising a secondaffordance representing a user prompt to power off the electronicdevice.

In some embodiments, a device comprises means for receiving datarepresenting an activation of a rotatable and depressible inputmechanism, the activation having an associated activation duration;means for determining whether the activation duration exceeds apredetermined threshold; means for determining a state of an activeapplication; and means for performing an action in accordance with adetermination that the activation duration exceeds the predeterminedthreshold and in accordance with a determination of the state of theactive application.

In some embodiments, a device comprises means for receiving datarepresenting an activation of a rotatable and depressible inputmechanism, the activation having an associated activation duration;means for displaying a first user interface screen, the first userinterface screen including a plurality of affordances, the plurality ofaffordances comprising an affordance representing an application inaccordance with a determination that the activation duration does notexceed the predetermined threshold; means for receiving second datarepresenting a second activation of the rotatable and depressible inputmechanism, the second activation having an associated second activationduration; means for determining whether the second activation durationexceeds a second predetermined threshold; and means for substituting thedisplay of the first user interface screen with a display of a seconduser interface screen, the second user interface screen including aclock face, in accordance with a determination that the secondactivation duration does not exceed the second predetermined threshold.

In some embodiments, a device comprises means for receiving first datarepresenting a first activation of a rotatable and depressible inputmechanism and a second activation of the rotatable and depressible inputmechanism, the first and the second activations having an associatedinterval between the first and the second activations; means responsiveto receiving the first data for determining whether the interval betweenthe first and the second activations exceeds a predetermined threshold;and means for invoking a previously invoked application in accordancewith a determination that the interval does not exceed the predeterminedthreshold.

In some embodiments, a device comprises means for receiving first datarepresenting an activation of a button, the activation having anassociated activation duration; means for determining whether theactivation duration exceeds a predetermined threshold; and means fordisplaying a user interface screen, the user interface screen includingat least a first affordance indicating a contact from a designated listof one or more contacts, wherein the designated list is a subset of afull list of contacts on the device in accordance with a determinationthat the activation duration does not exceed the predeterminedthreshold.

In some embodiments, a device comprises means for receiving first datarepresenting a first activation of a button and a second activation ofthe button, the first and the second activations having an associatedinterval between the first and the second activations; means fordetermining whether the interval between the first and the secondactivations exceeds a predetermined threshold; and means for invoking apayments application in accordance with a determination that theinterval does not exceed the predetermined threshold.

In some embodiments, a device comprises means for receiving datarepresenting an activation of a button and an activation of a rotatableand depressible input mechanism, wherein the activation of the buttonhas a first associated activation duration, wherein the activation ofthe rotatable and depressible input mechanism has a second associatedactivation duration and overlaps with the activation of the button foran overlap interval, and wherein the activation of the button and theactivation of the rotatable and depressible input mechanism are receivedsubstantially simultaneously; means for determining whether the datameet predetermined criteria; and means for rebooting the device inaccordance with a determination that the data meet the predeterminedcriteria.

In some embodiments, a device comprises means for receiving first datarepresenting an activation of a rotatable and depressible inputmechanism; means for determining whether the activation represents asingle press of the rotatable and depressible input mechanism, a doublepress of the rotatable and depressible input mechanism, or an extendedpress of the rotatable and depressible input mechanism; means fordisplaying a first user interface screen, the first user interfacescreen including a plurality of affordances, the plurality ofaffordances comprising an affordance representing an application inaccordance with a determination that the activation represents a singlepress of the rotatable and depressible input mechanism; means forinvoking a previously invoked application in accordance with adetermination that the activation represents a double press of therotatable and depressible input mechanism; means for determining a stateof an active application in accordance with a determination that theactivation represents an extended press of the rotatable and depressibleinput mechanism; and means for performing an action in accordance with adetermination of the state of the active application.

In some embodiments, a device comprises means for receiving first datarepresenting an activation of a button; means for determining whetherthe activation represents a single press of the button, a double pressof the button, or an extended press of the button; means for displayinga first user interface screen, the first user interface screen includingat least a first affordance indicating a contact from a designated listof one or more contacts, wherein the designated list is a subset of afull list of contacts on the device in accordance with a determinationthat the activation represents a single press of the button; means forinvoking a payments application in accordance with a determination thatthe activation represents a double press of the button; and means fordisplaying a second user interface screen, the second user interfacescreen comprising a second affordance representing a user prompt topower off the device in accordance with a determination that theactivation represents an extended press of the button.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having atouch-sensitive display in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A and 6B illustrate exemplary button functionalities for userinterfaces.

FIG. 7 illustrates exemplary button functionalities for user interfaces.

FIG. 8 illustrates exemplary button functionalities for user interfaces.

FIG. 9 illustrates exemplary button functionalities for user interfaces.

FIG. 10 illustrates exemplary button functionalities for userinterfaces.

FIG. 11 illustrates exemplary button functionalities for userinterfaces.

FIG. 12 illustrates exemplary button functionalities for userinterfaces.

FIG. 13 is a flow diagram illustrating a process for buttonfunctionalities for user interfaces.

FIG. 14 is a flow diagram illustrating a process for buttonfunctionalities for user interfaces

FIG. 15 is a flow diagram illustrating a process for buttonfunctionalities for user interfaces.

FIG. 16 is a flow diagram illustrating a process for buttonfunctionalities for user interfaces.

FIG. 17 is a flow diagram illustrating a process for buttonfunctionalities for user interfaces.

FIG. 18 is a flow diagram illustrating a process for buttonfunctionalities for user interfaces.

FIG. 19 is a flow diagram illustrating a process for buttonfunctionalities for user interfaces.

FIG. 20 is a flow diagram illustrating a process for buttonfunctionalities for user interfaces.

FIG. 21 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 22 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 23 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 24 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 25 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 26 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 27 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 28 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

As discussed above, a user may wish to access various user interfacesfor using different functions on a portable multifunction device.Providing functionalities for accessing such user interfaces withoutrelying solely on displayed icons may be beneficial for multifunctiondevices of any size by freeing the display for other features oraspects. Other input mechanisms such as buttons may these additionalfunctionalities, but it is highly desirable for such input mechanisms tobe intuitive (since their appearance typically does not change asreadily as a displayed object) and to allow for multifunctional use.Combinations of hardware buttons and rotatable and depressible inputmechanisms that are multifunctional alone and in combination are highlydesirable for providing different user interfaces on a portablemultifunction device.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for buttonfunctionalities for user interfaces. FIGS. 6-12 illustrate exemplarybutton functionalities for user interfaces. The user interfaces in thefigures are also used to illustrate the processes described below,including the processes in FIGS. 13-20 .

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2 ). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2 ) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2 ).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MIMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 1300-2000 (FIGS. 13-20). The computer-executable instructions can also be stored and/ortransported within any non-transitory computer-readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5 ). Forexample, an image (e.g., icon), a button, and text (e.g., hyperlink) mayeach constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

FIG. 6A shows exemplary button functionalities for user interfaces thatmay be operated on device 600. Device 600 may be device 100, 300, or 500in some embodiments. The electronic device has a display (e.g., 504). Asshown in FIG. 6A, device 600 includes rotatable and depressible inputmechanism 602. A rotatable and depressible input mechanism addsfunctionality to device 600 by providing multiple modes of useractivation, thereby increasing user interactivity and/or ease of usewith any of the user interfaces operable on device 600. The electronicdevice may also include a touch-sensitive surface (e.g., 504) and abutton (e.g., 508).

A user may activate rotatable and depressible input mechanism 602 byactivation 604. Depicted activation arrow blocks (e.g., activation 604)are typically not part of the displayed user interface, but are providedto aid in the interpretation of the figures. As depicted in FIG. 6A bythe arrow block, activation 604 has an associated activation duration(e.g., a duration of time during which the activation is continuouslydetected by the device). In response to receiving data representing theactivation, the device determines whether the activation durationexceeds a predetermined threshold. In some embodiments, thepredetermined threshold is a predetermined length of time. In responseto receiving data representing the activation, the device alsodetermines a state of an active application. An active application mayinclude a current application, a home screen of the device, a clock facedisplayed on the device, and so forth. For example, a state of a currentapplication could be a state of an application with which the user iscurrently interacting. Alternatively, a state of an active applicationcould refer to a currently displayed screen on the device, such as aclock face or a home screen.

In accordance with a determination that the activation duration exceedsthe predetermined threshold (e.g., the input is an extended press ofrotatable and depressible input mechanism 602, as depicted by the longarrow block shown for activation 604), and in accordance with adetermination of the state of the active application, the deviceperforms an action. In some embodiments, the action may be related orotherwise corresponding to the state of the active application. Forexample, the device may perform an action that is related to thecurrently displayed content or user interface of the device. In thisway, the rotatable and depressible input mechanism may provide differentfunctionalities depending on how the user is interacting with the device(e.g., a displayed user interface).

In some embodiments, a rotatable and depressible input mechanism (e.g.,602) is a mechanical button that is rotatable, and the activation is aphysical depression of the mechanical button. In some embodiments, arotatable and depressible input mechanism (e.g., 602) is a capacitivebutton that is rotatable, and the activation is a touch on thecapacitive button. In either case, the rotatable and depressible inputmechanism retains two modes of user interaction, which advantageouslymay be used for different purposes. In some embodiments, the activation(e.g., 604) does not represent a rotation of the rotatable anddepressible input mechanism. In some embodiments, detection of theactivation is based on detecting a press such as a physical depressionor a touch and does not require a rotation for detection. For example,the device may perform an action in response to an activation ofrotatable and depressible input mechanism 602, and it may scroll orcycle through content or options based on the action in response to arotation.

In some embodiments, in accordance with a determination that the stateof the active application relates to user-to-user voice communication,the device may invoke an application for low-latency asynchronous voicecommunication (e.g., a walkie talkie-type function). For example, if theactive application provides a voice communication interface, an extendedpress of the rotatable and depressible input mechanism could activate alow-latency asynchronous voice communication functionality.

In some embodiments, after invoking the application for low-latencyasynchronous voice communication, the device receives a voice input andtransmits the voice input to a second electronic device capable ofreceiving the voice input. As an illustrative example, in thelow-latency asynchronous voice communication application, a user mayspeak while activating the rotatable and depressible input mechanism foran extended press, listen to a response from the second device while therotatable and depressible input mechanism is not being activated, thenspeak again while activating the rotatable and depressible inputmechanism for an extended press.

In some embodiments, in accordance with a determination that the stateof the active application relates to transcribing a voice input, thedevice may invoke a dictation application, receive a voice input, andtranscribe the voice input into a displayed text. For example, if theuser is in a state of an application that receives text input (e.g.,from a physical or virtual keyboard, such as a notes application), anextended press on the rotatable and depressible input mechanism mayinvoke a dictation application to receive instead a speech input fromthe user, which can be transcribed by the device into displayed text. Asshown in FIG. 6A, device 600 has received a voice input and showsdisplayed text 606, which was transcribed from the voice input.

In some embodiments, in accordance with a determination that the stateof the active application relates to audio messaging, the device mayinvoke an audio messaging application, record a voice input, and senddata representing the recorded voice input to a second electronic devicecapable of receiving the data. For example, if the user is in a textmessaging application, an extended press on the rotatable anddepressible input mechanism may invoke an audio messaging application tosend an audio file to a recipient (e.g., a participant in a textmessaging conversation).

In some embodiments, in accordance with a determination that the stateof the active application relates to receiving a voice request toexecute a task, or in accordance with a determination that the state ofthe current application does not relate to user-to-user voicecommunication or transcribing a voice input, the device may invoke avirtual assistant. Further description of a virtual assistant may befound, for example, in related application U.S. Utility application Ser.No. 12/987,982, entitled “Intelligent Automated Assistant,” filed Jan.10, 2011 application.

For example, if the user is in a state of an application for executing atask, the device may invoke the virtual assistant to execute the task.Alternatively, invoking a virtual assistant may represent a default,such that the device may invoke a virtual assistant upon receiving anextended press of the rotatable and depressible input mechanism whilethe user is in any state of any application not explicitly assigned toinvoke a different function. As described above, the functionalitiesinvoked by an extended press of the rotatable and depressible inputmechanism all relate to a speech or voice input. This unites thefunctions invokable through an extended press of the rotatable anddepressible input mechanism by a common general feature, which helps thecomprehensibility and intuitiveness of the device. Further, this allowsfor invoking multiple features through the same user input bydetermining which feature to invoke dependent upon a state of an activeapplication. A user may be more likely to want to invoke a particularfunction if the user is in a state of an active application that isrelated to the function.

In some embodiments, after invoking the virtual assistant, the devicedisplays a user interface screen on the display. This user interfacescreen includes a user prompt for voice input. A user prompt for voiceinput may include a text prompting the user to enter a voice input or anaffordance representing a voice input (such as a microphone, speechballoon, or other depiction related to a voice input). As used here, theterm “affordance” refers to a user-interactive graphical user interfaceobject that may be displayed on the display screen of device 100, 300,and/or 500 (FIGS. 1, 3, and 5A). For example, an image (e.g., icon), avirtual button, and text may each constitute an affordance. In someembodiments, the device may further receive a voice input.

In some embodiments, after receiving the voice input, the devicetranscribes the voice input into text and displays the text on thedisplay. For example, in FIG. 6A, device 600 has transcribed a voiceinput from the user and displayed transcribed text (e.g., 606) based onthe voice input on the display. In some embodiments, the device alsodisplays a waveform based on the voice input on the display (e.g.,waveform 608). A waveform based on a voice input may graphicallyrepresent a sound wave, but it need not depict a sound wave that isprecisely based on the physical characteristics of the voice input(e.g., the waveform may not be a mathematical representation of theactual sound wave of the voice input). In some embodiments, the waveformis a stylized representation of a sound wave sufficient to connote tothe user that the voice input is received by the device. In someembodiments, one or more characteristics of the waveform is based on aphysical characteristic of the voice input (e.g., frequency, amplitude,wave length, and so forth).

In some embodiments, the device displays the waveform on the display ata position adjacent to the rotatable and depressible input mechanism(e.g., a portion of the waveform is at a position proximal to therotatable and depressible input mechanism). As shown in FIG. 6A,waveform 608 is displayed by device 600 at a position next to rotatableand depressible input mechanism 602. Advantageously, this helps the userrecognize that activation of the rotatable and depressible inputmechanism invokes an application for receiving a voice input depicted bythe waveform, thereby increasing the usability and intuitive feel of theinterface through the rotatable and depressible input mechanismfunctionality.

In some embodiments, the device determines whether the voice inputcontains a request to execute a task executable by the virtualassistant, and in accordance with a determination that the voice inputcontains a request to execute a task executable by the virtualassistant, the device executes the task by the virtual assistant.Further details on this determination and tasks executed by a virtualassistant may be found in the related application cited above.

An embodiment of these concepts is illustrated in FIG. 6B. FIG. 6B showsdevice 600 receiving a voice input with a request to text Adrian “Do youhave time for coffee.” Device 600 has transcribed this voice requestinto displayed texts 614 and 624 on user interface screens 610 and 620,respectively. Waveform 612 is displayed on user interface screen 610next to rotatable and depressible input mechanism 616. As illustrated bythe transition from user interface screen 610 to user interface screen620, waveform 612 is animated to appear as if emanating from rotatableand depressible input mechanism 616, as it progresses fully across thedisplay as waveform 622 on user interface screen 620, which ispositioned next to rotatable and depressible input mechanism 626.Similar to what was described above, this animation further strengthensthe user's connection between the rotatable and depressible inputmechanism itself and its functionality.

In some embodiments, the virtual assistant is run on the electronicdevice. In some embodiments, the virtual assistant is run on an externaldevice in wireless communication with the electronic device. As usedherein, invoking a virtual assistant, determining whether a voice inputcontains a request to execute a task executable by the virtualassistant, and/or executing a task using a virtual assistant may beperformed on or by the device itself or by wirelessly communicating withone or more external devices, such as an electronic device (e.g., aphone, laptop, desktop, or tablet computer), server, and the like. Forexample, the device may execute a task on an external device or by usingdata from an external device. One or more of the functions required toexecute the task (e.g., receiving a voice input, determining whether thevoice input contains a request to execute a task, determining whetherthe task is executable by the virtual assistant, and executing the task)may be performed on an external device in wireless communication withthe device (e.g., device 600) using data from the device and/or bysending data to the device.

In some embodiments, the device may send first data representing thevoice input to an external device, receive from the external devicesecond data representing a request to execute a task executable by thevirtual assistant, transcribe the request into text, and display thetext on the display (e.g., text 608, 614, or 624). The device mayreceive the second data via wireless communication (e.g., Wi-Fi,Bluetooth™, near field communication (“NFC”), cellular and/or otherwireless communication techniques, and so forth).

In some embodiments, the device displays an affordance representing auser prompt to display additional data related to the request on anexternal device. That is to say, the device may indicate to the userthat additional data may be viewed on the external device, which may beparticularly advantageous if the electronic device has a display smallerthan the display of the external device. Additional data related to therequest may include further or more detailed data requested by the user.For example, if the request is for weather information, the device maydisplay weather information such as a predicted or current weathercondition, temperature, and the like, and the user may view moredetailed weather information (such as moon phase, humidity, barometricpressure, a weekly forecast, and so forth) on the external device.

In some embodiments, a rotatable and depressible input mechanism mayinclude any of the functionalities described above in combination withone or more of the other functionalities described herein for arotatable and depressible input mechanism. In some embodiments, device600 may also include a button (e.g., 508) with one or more of thefunctionalities described herein for a button.

FIG. 7 shows exemplary button functionalities for user interfaces thatmay be operated on device 700. Device 700 may be device 100, 300, or 500in some embodiments. The electronic device has a display (e.g., 504). Asshown in FIG. 7 , device 700 includes rotatable and depressible inputmechanism 702. The electronic device may also include a touch-sensitivesurface (e.g., 504) and a button (e.g., 508).

A user may activate rotatable and depressible input mechanism 702 byactivation 704. As depicted in FIG. 7 by the arrow block, activation 704has an associated activation duration. In response to receiving datarepresenting the activation, the device determines whether theactivation duration exceeds a predetermined threshold. In someembodiments, the predetermined threshold is a predetermined length oftime.

In accordance with a determination that the activation duration does notexceed the predetermined threshold (e.g., the input is a single press ofrotatable and depressible input mechanism 702, as depicted by the short,single arrow block shown for activation 704), the device displays afirst user interface screen including a plurality of affordances on thedisplay. For example, device 700 displays user interface screen 706 thatincludes a plurality of affordances that includes affordances 708 and710. In the plurality, at least a first affordance represents anapplication. For example, the affordance may be an affordance such as anicon that, when activated, causes the application to be displayed (e.g.,affordances may include user-interactive icons for launching a softwareapplication). An affordance representing an application may convey tothe user the application through texts, symbols, icons, depictions of anapplication-related screen, or any other visual indication thatrepresents the application. In some embodiments, user interface screen706 may be a home screen that includes a plurality of affordancesrepresenting applications.

While the first user interface screen is displayed, a user may activaterotatable and depressible input mechanism 702 with a second activationhaving a second activation duration. In response to receiving the data,the device determines whether the second activation duration exceeds asecond predetermined threshold. In accordance with a determination thatthe second activation duration does not exceed the second predeterminedthreshold (e.g., the input is a single press of the rotatable anddepressible input mechanism), the device displays a second userinterface screen (e.g., 720) that includes a clock face (e.g., 722). Insome embodiments, the order of screens may be reversed, such that afirst single press causes the display of a clock face (e.g., 722), and asecond single press causes the display of a plurality of applicationaffordances (e.g., 708 and 710). Linking these functions allows the userto easily navigate between a clock face and application affordances,which is advantageous if the user uses the device to keep time and touse applications.

In some embodiments, the device displays a user interface screen thatincludes a clock face. While the user interface screen is displayed, auser may activate rotatable and depressible input mechanism 702 with athird activation having a third activation duration. In response toreceiving the data, the device determines whether the third activationduration exceeds a third predetermined threshold. In accordance with adetermination that the third activation duration does not exceed thethird predetermined threshold (e.g., the input is a single press of therotatable and depressible input mechanism), the device displays a seconduser interface screen that includes a plurality of affordances on thedisplay.

In some embodiments, a rotatable and depressible input mechanism (e.g.,702) is a mechanical button that is rotatable, and the activation is aphysical depression of the mechanical button. In some embodiments, arotatable and depressible input mechanism (e.g., 702) is a capacitivebutton that is rotatable, and the activation is a touch on thecapacitive button. In some embodiments, the activation (e.g., 704) doesnot represent a rotation of the rotatable and depressible inputmechanism. In some embodiments, detection of the activation is based ondetecting a press such as a physical depression or a touch and does notrequire a rotation for detection. For example, the device may perform anaction in response to an activation of 702, and it may scroll or cyclethrough content or options based on the action in response to arotation.

In some embodiments, a clock face displayed by the device includes auser interface object that indicates time. In some embodiments, thedevice displays an affordance based on the user interface object on thefirst user interface screen. For example, the affordance may be the sameobject as the user interface object but smaller, or it may beapproximately the same object but with fewer details, to accommodate asmaller display size (i.e., since the affordance screen has a pluralityof affordances, the affordance representing the user interface objectmay be smaller than the user interface object when displayed as part ofa clock face).

In some embodiments, the user interface object and the affordance mayrepresent a similar meaning to the user without being the same object.For example, the user interface object may be a representation of adigital clock, and the first affordance may be a representation of ananalog clock. In this case, the analog clock may convey a notion oftimekeeping to the user more clearly than a pair of numbers (as with adigital clock), particularly on a reduced size display. In someembodiments, the user interface object and the affordance may displaythe same time. In some embodiments, the user interface object and theaffordance may display different times. For example, the user interfaceobject may display a time of interest, such as a current time, whereasthe affordance may display a generic time (e.g., 10:10) as an indicationto the user that activating it leads to a display of the clock face.That is to say, the affordance may simply represent the idea oftimekeeping to the user so that the user recognizes that activation ofthe affordance displays a clock face.

In some embodiments, a single press of the rotatable and depressibleinput mechanism acts as a back button for the device, such that a singlepress may return the user to the most previously displayed screen in anyinterface of the device.

In some embodiments, the time indicated by the user interface object isa current time. In some embodiments, the affordance indicates a currenttime.

In some embodiments, the user interface object is a representation of ananalog clock that includes an hour hand and a minute hand. In someembodiments, the user interface object is a representation of a digitalclock with a numerical indication of an hour and a numerical indicationof a minute. In some embodiments, the affordance is a representation ofan analog clock that includes an hour hand and a minute hand. In someembodiments, the affordance is a representation of a digital clock witha numerical indication of an hour and a numerical indication of aminute.

In some embodiments, the predetermined threshold for the firstactivation duration is the same as the predetermined threshold for thesecond activation duration. This provides a consistent threshold to theuser for interactions with the device.

In some embodiments, the first activation and the second activation havean associated interval of time between them, and this interval exceeds athird predetermined threshold (e.g., 0.5 seconds, 1 second, or 2seconds). This allows the device to distinguish between sequentialsingle presses and a double press (described below).

In some embodiments, a rotatable and depressible input mechanism mayinclude any of the functionalities described above in combination withone or more of the other functionalities described herein for arotatable and depressible input mechanism. In some embodiments, device700 may also include a button (e.g., 508) with one or more of thefunctionalities described herein for a button.

FIG. 8 shows exemplary button functionalities for user interfaces thatmay be operated on device 800. Device 800 may be device 100, 300, or 500in some embodiments. The electronic device has a display (e.g., 504). Asshown in FIG. 8 , device 800 includes rotatable and depressible inputmechanism 802. The electronic device may also include a touch-sensitivesurface (e.g., 504) and a button (e.g., 508).

A user may activate rotatable and depressible input mechanism 802 byactivation 804. As depicted in FIG. 8 by the arrow blocks, activation804 has a first activation and a second activation with an associatedinterval between the first and the second activations. In response toreceiving data representing the first and second activations, the devicedetermines whether the interval between the first and the secondactivations exceeds a predetermined threshold. In some embodiments, thepredetermined threshold is a predetermined length of time.

In accordance with a determination that the interval does not exceed thepredetermined threshold (e.g., a double press, rather than twosequential single presses), the device invokes a previously invokedapplication. FIG. 8 shows an application user interface screen 806displayed by device 800 in response to double press 804 on rotatable anddepressible input mechanism 802. A previously invoked application mayinclude any application previously invoked on the device.

In some embodiments, the previously invoked application is the latestinvoked application that is not currently displayed. As an illustrativeexample, the user may invoke a calendar application, then switch to aweather application. In this example, while the weather application isdisplayed, the user may invoke and display the calendar application witha double press on the rotatable and depressible input mechanism.

In some embodiments, a rotatable and depressible input mechanism (e.g.,802) is a mechanical button that is rotatable, and the first and thesecond activations are physical depressions of the mechanical button. Insome embodiments, a rotatable and depressible input mechanism (e.g.,802) is a capacitive button that is rotatable, and the first and thesecond activations are touches on the capacitive button. In someembodiments, the first and the second activations (e.g., 804) do notinclude a rotation of the rotatable and depressible input mechanism. Insome embodiments, detection of the activation is based on detecting apress such as a physical depression or a touch and does not require arotation for detection. For example, in some embodiments, the device mayinvoke a previously invoked application by a double press of therotatable and depressible input mechanism, then scroll or cycle throughapplication content or other application data in response to a rotationof the rotatable and depressible input mechanism.

In some embodiments, the previously invoked application is invoked in anapplication start state. For example, in response to a double press of802, the device may start a previously invoked application and displaythe application start screen, as shown in FIG. 8 . In some embodiments,the previously invoked application is invoked in a previous applicationstate. In some embodiments, the previous application state correspondsto a state of the application after a user interaction. For example, ifthe user leaves the application in a particular state, then switches toanother application, a double press of 802 would return the user to theparticular state. If the user leaves the application on a particularscreen, then switches to another application, a double press of 802would return the user to the particular screen.

In some embodiments, the previously invoked application is invoked in astored application state. For example, the user may save a particularstate of an application and return to the state through a double pressof 802.

In some embodiments, a rotatable and depressible input mechanism mayinclude any of the functionalities described above in combination withone or more of the other functionalities described herein for arotatable and depressible input mechanism. In some embodiments, device800 may also include a button (e.g., 508) with one or more of thefunctionalities described herein for a button.

FIG. 9 shows exemplary button functionalities for user interfaces thatmay be operated on device 900. Device 900 may be device 100, 300, or 500in some embodiments. The electronic device has a display (e.g., 504). Asshown in FIG. 9 , device 900 includes button 902. The electronic devicemay also include a touch-sensitive surface (e.g., 504) and a rotatableand depressible input mechanism (e.g., 506, 602, 702, or 802).

A user may activate button 902 by activation 904. As depicted in FIG. 9by the arrow block, activation 904 has an associated activationduration. In response to receiving data representing the activation, thedevice determines whether the activation duration exceeds apredetermined threshold. In some embodiments, the predeterminedthreshold is a predetermined length of time.

In accordance with a determination that the activation duration does notexceed the predetermined threshold (e.g., the input is a single press ofbutton 902, as depicted by the short, single arrow block shown foractivation 904), the device displays a user interface screen thatincludes at least a first affordance indicating a contact from adesignated list of one or more contacts, wherein the designated list isa subset of a full list of contacts on the electronic device. Forexample, FIG. 9 shows user interface screen 906 that includes severalaffordances indicating contacts, such as affordance 908 that indicates acontact “Katie.” Contacts may be indicated by a text such as a name oran image (e.g., a user- or system-designated image associated with thecontact or with a contact entry for the contact).

In some embodiments, a button (e.g., 902) is a mechanical button, andthe activation is a physical depression of the mechanical button. Insome embodiments, a button (e.g., 902) is a capacitive button, and theactivation is a touch on the capacitive button.

In some embodiments, the designated list of contacts is different fromother sets of contacts, such as VIPs (very important persons) orfavorites. For example, in some embodiments, the designated list ofcontacts may be contacts with whom the user has an emotional connection.This functionality provides methods of communicating with thesedesignated contacts (described below) that are more informal, intimate,and/or frequent than those used for other sets of contacts like VIPs,which may be a more practical set of contacts and means of communication(e.g., email). By providing these functionalities of communicating withcontacts with whom the user is emotionally connected, the connectionbetween the device and the user is strengthened and extends beyondpurely productivity- or work-related functions.

This button functionality allows the user to quickly access a userinterface screen that includes affordance(s) indicating contact(s) froma designated list of one or more contacts. It is to be noted that, insome embodiments, this screen is accessed by a single press on thebutton, similar to the single press on the rotatable and depressibleinput mechanism, which in some embodiments allows the user to access auser interface screen that includes a plurality of affordancesrepresenting application(s). These parallel functionalities enhance theusability and intuitive feel of the device by providing access toconceptual similar functionalities (e.g., a designated contacts “homescreen” and an applications “home screen”) through similar types ofinputs (e.g., a single press on the button and a single press on therotatable and depressible input mechanism).

In some embodiments, the designated list of contacts is based on atleast one of the following: time of day of interactions between the userand a contact (e.g., designated contacts may have more interactions withthe user outside of typical weekday working hours relative to othercontacts), frequency of interactions between the user and a contact(e.g., designated contacts may have an increased frequency ofinteractions with the user relative to other contacts), and length ofinteractions between the user and a contact (e.g., designated contactsmay have longer interactions with the user relative to other contacts).

In some embodiments, the designated list of contacts is user-designated.For example, the device may provide a selection interface for the userto select contacts for the designated list of contacts.

In some embodiments, while the user interface screen is displayed, thedevice may receive second data representing a touch (e.g., a singlepress) on the touch-sensitive display at the location of an affordancecorresponding to a contact. In response to receiving the second data,the device invokes a user prompt for selecting an application configuredto provide a mode of interaction with the contact.

In some embodiments, the application configured to provide a mode ofinteraction with the contact is a text messaging application for sendinga text to the contact. Advantageously, this functionality allows theuser to quickly send a text to a designated contact without needing toenter a text messaging interface and then select the designated contact,allowing the user to interact with a designated contact more easily. Insome embodiments, the application configured to provide a mode ofinteraction with the contact is a low-latency asynchronous voicecommunication application for opening low-latency asynchronous voicecommunication with the contact. In some embodiments, the applicationconfigured to provide a mode of interaction with the contact is anapplication for sending a drawing to a contact.

This button functionality allows the user to select a designatedcontact, then select a mode of interaction, rather than selecting themode of interaction (e.g., by opening an application), then selectingthe contact. Advantageously, this makes it easier for the user tointeract with a contact, e.g., a contact with whom the user mayfrequently interact or with whom the user may be more eager to interact.That is to say, this functionality may improve the user interface withthe device by allowing the user to prioritize a particular contactthrough quicker access to the contact, rather than forcing the user tofirst select the specific application for the interaction.

In some embodiments, while the user interface screen is displayed, thedevice receives third data representing a second touch on thetouch-sensitive display at the location of a portion representing acontact and a third touch on the touch-sensitive display at the locationof a portion representing a contact. The second and third touches areseparated by an associated duration interval. In response to detectingthe touches, the device determines whether the duration interval is lessthan a predetermined duration, and in accordance with a determinationthat the duration interval is less than the predetermined duration(e.g., a double touch on the portion representing the contact), thedevice provides an interface configured to receive data representing auser input and send a signal to a second electronic device. For example,in some embodiments, a user viewing the user interface screen mayactivate a display of a contact with a single tap to provide a mode ofinteraction with the contact (as described above), or the user mayactivate a display of a contact with a single tap to enter theinterface.

The signal represents an instruction instructing the second electronicdevice to generate a haptic alert based on the data. In someembodiments, the user input represented by the data includes a touch onthe touch-sensitive display. For example, if the data represent a seriesof touches on the display in a particular pattern, the haptic alertgenerated could be based on the particular pattern of touches.Therefore, this interface provides a way for the user to send acustomizable haptic alert to a designated contact. This furtherreinforces the idea that the designated contacts are contacts with whomthe user has an emotional connection by allowing the user to send atangible message to the contact, even if the user and the contact areapart.

Attention is now directed to FIG. 10 , which shows exemplary buttonfunctionalities for user interfaces that may be operated on device 1000.Device 1000 may be device 100, 300, or 500 in some embodiments. Theelectronic device has a display (e.g., 504). As shown in FIG. 10 ,device 1000 includes button 1002. The electronic device may also includea touch-sensitive surface (e.g., 504) and a rotatable and depressibleinput mechanism (e.g., 506, 602, 702, or 802).

As described above, in accordance with a determination that anactivation of the button is a single press, the device displays a userinterface screen that includes at least a first affordance indicating acontact from a designated list of one or more contacts. In someembodiments, in accordance with a determination that the activationduration of the button activation exceeds the predetermined threshold(e.g., an extended press on the button), the device substitutes the userinterface screen with a second user interface screen that includes anaffordance representing a user prompt to power off the electronicdevice.

For example, as depicted in FIG. 10 , a user may activate button 1002 byactivation 1004. As depicted by the long arrow block, activation 1004 isan extended press of button 1002. In response to receiving datarepresenting activation 1004, the device displays user interface screen1006, which includes affordance 1008. Affordance 1008 represents a userprompt to power off the electronic device. A user may tap, swipe, orotherwise activate affordance 1008 to power off the electronic device.

In some embodiments, screen 1006 also includes an affordancerepresenting a user prompt to enter a power-saving mode of theelectronic device (e.g., affordance 1010). In some embodiments,power-saving mode includes altering the device display (e.g., alteringthe color and/or brightness of one or more pixels) to reduce powerconsumption. In some embodiments, power-saving mode includes alteringthe function of one or more device components to reduce powerconsumption. For example, the device may alter or reduce the function ofone or more RF circuitry components (such as wireless transceivers,Wi-Fi components, Bluetooth components, or other components that sendand receive signals to and from external devices or servers), speakers,GPS sensor, accelerometer, directional sensor, gyroscope, motion sensorand/or other components of the device that consume power. In someembodiments, power consumption refers to battery power consumption. Auser may tap, swipe, or otherwise activate affordance 1010 to enter apower-saving mode of the electronic device.

In some embodiments, screen 1006 also includes an affordancerepresenting a user prompt to turn off the touch-sensitive display(e.g., affordance 1012). A user may tap, swipe, or otherwise activateaffordance 1012 to turn off the touch-sensitive display.

In any of the embodiments described herein, the device may turn on thedisplay in response to a user movement of the device (e.g., a wristraise, lifting and/or rotation of the device, or any other indicationthat the user has moved the position of the device for viewing thedisplay). As described above, the device may include various sensors,such as accelerometer 534, gyroscope 536, and motion sensor 538, thatmay allow the device to detect a user movement of the device. These canbe operatively connected to I/O section 514, which could send a signalto the display to turn on the display. The device may also be configuredto use these components to control turning off the display. In someembodiments, a lack of a specific motion input for a predeterminedduration of time may cause the device to turn off the display.

In addition to any of these functionalities, allowing the user tofurther control the display through affordance 1012 is advantageousbecause some users may not be as capable of generating specificmovements of the device configured to turn on or turn off the display.For example, if the user has interacts with or wears the device on aprosthetic limb, or uses a prosthetic limb to hold the device, themovements of the prosthetic limb may not generate the same types ofmovement that the device is configured to detect. Advantageously, thisfunctionality makes the device more usable for disabled users andincreases compliance with, e.g., the Americans with Disabilities Act.

In some embodiments, the device may be configured to detect theintensity of touches. This functionality is described in greater detail,for example, in reference to touchscreen 504 above. Techniques fordetecting and processing touch intensity may be found, for example, inrelated applications: International Patent Application Serial No.PCT/US2013/040061, entitled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013 and International Patent ApplicationSerial No. PCT/US2013/069483, entitled “Device, Method, and GraphicalUser Interface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013.

In some embodiments, while user interface screen 1006 is displayed,device 1000 detects a first touch on the touch-sensitive display with afirst characteristic intensity. In response to detecting the firsttouch, the device determines whether the first characteristic intensityis above an intensity threshold. In response to a determination that thefirst characteristic intensity is above the intensity threshold, thedevice executes a separate function of the electronic device. As usedhere, a “separate function” of the electronic device may refer to anydevice function not specifically ascribed to a rotatable and depressibleinput mechanism interaction or a button interaction described herein.

In some embodiments, when the device is powered off when the extendedpress of the button is received, and in accordance with a determinationthat the activation duration of the button activation exceeds thepredetermined threshold (e.g., an extended press on the button), thedevice powers on. As described above, an extended press on the buttonmay serve to power on or power off the device, depending on the state ofthe device when the button activation is detected.

In some embodiments, a button may include any of the functionalitiesdescribed above in combination with one or more of the otherfunctionalities described herein for a button. In some embodiments,device 900 and/or device 1000 may also include a rotatable anddepressible input mechanism (e.g., 506, 602, 702, or 802) with one ormore of the functionalities described herein for a rotatable anddepressible input mechanism.

FIG. 11 shows exemplary button functionalities for user interfaces thatmay be operated on device 1100. Device 1100 may be device 100, 300, or500 in some embodiments. The electronic device has a display (e.g.,504). As shown in FIG. 11 , device 1100 includes button 1102. Theelectronic device may also include a touch-sensitive surface (e.g., 504)and a rotatable and depressible input mechanism (e.g., 506, 602, 702, or802).

A user may activate button 1102 by activation 1104. As depicted in FIG.11 by the arrow blocks, activation 1104 has a first activation and asecond activation with an associated interval between the first and thesecond activations. In response to receiving data representing the firstand second activations, the device determines whether the intervalbetween the first and the second activations exceeds a predeterminedthreshold. In some embodiments, the predetermined threshold is apredetermined length of time.

In accordance with a determination that the interval does not exceed thepredetermined threshold (e.g., a double press, rather than twosequential single presses), the device invokes a payments application.Further descriptions of exemplary payments applications may be found,for example in the related application U.S. Application Ser. No.62/004,886, entitled “User Interface for Payments,” filed May 29, 2014.

FIG. 11 shows a payments application user interface screen displayed bydevice 1100 in response to double press 1104 on button 1102. In someembodiments, invoking an application (e.g., a payments application) mayinclude invoking and/or displaying an application that is alreadyrunning. In some embodiments, double press 1104 may invoke a differentstate or screen of an already running and/or displayed application.

In some embodiments, the button (e.g., 1102) is a mechanical button, andboth of the first and the second activations represent depressions ofthe mechanical button. In some embodiments, the button (e.g., 1102) is acapacitive button, and both of the first and the second activationsrepresent touches on the capacitive button.

In some embodiments, the device displays a user interface screen thatincludes an affordance representing a mode of payment. In someembodiments, the mode of payment is a credit card. In some embodiments,the affordance depicts a visual representation of the face of the creditcard, indicating a credit card number and a credit card company. Asshown in FIG. 11 , device 1100 displays affordance 1106, whichrepresents a credit card. The credit card itself is indicated by thedisplayed credit card company name 1108 and the displayed credit cardnumber 1110. In some embodiments, the credit card company and creditcard number correspond to a user's credit card account.

In some embodiments, the mode of payment is a debit card. In someembodiments, the affordance depicts a visual representation of the faceof the debit card, indicating a debit card number and a debit card bank.In some embodiments, the debit card bank and debit card numbercorrespond to a user's debit account.

In some embodiments, the mode of payment is a bank account. In someembodiments, the affordance indicates at least one of a bank associatedwith the bank account, a type of the bank account, and a bank accountnumber associated with the bank account. In some embodiments, the bankaccount is a checking account. In some embodiments, the bank account isa savings account.

This functionality allows the user to quickly invoke a paymentsapplication through an input (e.g., a double press of the button). It isto be noted that, in some embodiments, this application is invoked by adouble press on the button, similar to the double press on the rotatableand depressible input mechanism, which in some embodiments allows theuser to invoke a previously invoked application. These parallelfunctionalities enhance the usability and intuitive feel of the deviceby providing access to conceptual similar functionalities (e.g.,applications) through similar types of inputs (e.g., a double press onthe button and a double press on the rotatable and depressible inputmechanism).

In some embodiments, a button may include any of the functionalitiesdescribed above in combination with one or more of the otherfunctionalities described herein for a button. In some embodiments,device 1100 may also include a rotatable and depressible input mechanism(e.g., 506, 602, 702, or 802) with one or more of the functionalitiesdescribed herein for a rotatable and depressible input mechanism.

FIG. 12 shows exemplary button functionalities for user interfaces thatmay be operated on device 1200. Device 1200 may be device 100, 300, or500 in some embodiments. The electronic device has a display (e.g.,504). As shown in FIG. 12 , device 1200 includes button 1202 androtatable and depressible input mechanism 1204. The electronic devicemay also include a touch-sensitive surface (e.g., 504).

A user may activate button 1202 and rotatable and depressible inputmechanism 1204 by activations 1206 and 1208, respectively. Activation1206 has a first associated activation duration, and activation 1208 hasa second associated activation duration. As depicted in FIG. 12 ,activations 1206 and 1208 are received substantially simultaneously,such that activation 1208 overlaps with activation 1206 for an overlapinterval.

In response to receiving the data, the device determines whether thedata meet predetermined criteria. In accordance with a determinationthat the data meet the predetermined criteria, the device reboots. Insome embodiments, the reboot is a hard reboot. In some embodiments, thereboot is a soft reboot.

In some embodiments, the rotatable and depressible input mechanism(e.g., 1204) is a mechanical button that is rotatable, and theactivation of the rotatable and depressible input mechanism includes adepression of the mechanical button. In some embodiments, the rotatableand depressible input mechanism (e.g., 1204) is a capacitive button thatis rotatable, and the activation of the rotatable and depressible inputmechanism includes a touch on the capacitive button. In someembodiments, the activation of the rotatable and depressible inputmechanism (e.g., 1208) does not include a rotation of the rotatable anddepressible input mechanism. In some embodiments, detection of theactivation is based on detecting a press such as a physical depressionor a touch and does not require a rotation for detection.

In some embodiments, the button (e.g., 1202) is a mechanical button, andthe activation of the button includes a depression of the mechanicalbutton. In some embodiments, the button (e.g., 1202) is a capacitivebutton, and wherein the activation of the button includes a touch on thecapacitive button.

In some embodiments, the predetermined criteria relate to the first andsecond activation durations. In some embodiments, device 1200 determineswhether both the first and the second activation durations exceed apredetermined threshold, and in accordance with a determination thatboth the first and the second activation durations exceed thepredetermined threshold (e.g., extended presses on button 1202 androtatable and depressible input mechanism 1204), the device reboots. Insome embodiments, the predetermined threshold is a predetermined lengthof time.

In some embodiments, the predetermined criteria relate to the overlapinterval. In some embodiments, device 1200 determines whether overlapinterval exceeds a second predetermined threshold, and in accordancewith a determination that the overlap interval exceeds the secondpredetermined threshold (e.g., substantially simultaneous extendedpresses on button 1202 and rotatable and depressible input mechanism1204), the device reboots.

In some embodiments, a button and/or a rotatable and depressible inputmechanism may include any of the functionalities described above incombination with one or more of the other functionalities describedherein for a button and/or a rotatable and depressible input mechanism.

In some embodiments, an electronic device (e.g., multifunction device500) may have a rotatable and depressible input mechanism (e.g., 602,616, 626, 702, 802, or 1204) with one of more of the associatedfunctionalities described herein and a button (e.g., 902, 1002, 1102, or1202) with one of more of the associated functionalities describedherein. The electronic device has a display (e.g., 504). The electronicdevice may also include a touch-sensitive surface (e.g., 504). In someembodiments, the device receives data representing an activation of therotatable and depressible input mechanism and determines whether theactivation represents a single press of the rotatable and depressibleinput mechanism (as described above), a double press of the rotatableand depressible input mechanism (as described above), or an extendedpress of the rotatable and depressible input mechanism (as describedabove). In accordance with a determination that the activationrepresents a single press of the rotatable and depressible inputmechanism, the device displays a first user interface screen on thedisplay, the first user interface screen including a plurality ofaffordances with an affordance representing an application. Inaccordance with a determination that the activation represents a doublepress of the rotatable and depressible input mechanism, the deviceinvokes a previously invoked application. In accordance with adetermination that the activation represents an extended press of therotatable and depressible input mechanism, the device determines a stateof an active application, and in accordance with a determination of thestate of the active application, the device performs an action. In someembodiments, the device receives data representing an activation of thebutton and determines whether the activation represents a single pressof the button (as described above), a double press of the button (asdescribed above), or an extended press of the button (as describedabove). In accordance with a determination that the activationrepresents a single press of the button, the device displays a firstuser interface screen including at least a first affordance indicating acontact from a designated list of one or more contacts, where thedesignated list is a subset of a full list of contacts on the electronicdevice. In accordance with a determination that the activationrepresents a double press of the button, the device invokes a paymentsapplication. In accordance with a determination that the activationrepresents an extended press of the button, the device displays a seconduser interface screen that includes a user prompt to power off theelectronic device. In some embodiments, the device receives datarepresenting an activation of the button and an activation of therotatable and depressible input mechanism, determines whether the datameet predetermined criteria, and in accordance with a determination thatthe data meet the predetermined criteria, the device reboots.

FIG. 13 is a flow diagram illustrating process 1300 for buttonfunctionalities for user interfaces. In some embodiments, process 1300may be performed at an electronic device with a touch-sensitive displayand a rotatable and depressible input mechanism, such as device 500(FIG. 5 ) or device 600 (FIGS. 6A and 6B). Some operations in method1300 may be combined, the order of some operations may be changed, andsome operations may be omitted.

At block 1302, the device receives data representing an activation ofthe rotatable and depressible input mechanism with an associatedactivation duration. At block 1304, a determination is made as towhether the activation duration exceeds a predetermined threshold. Atblock 1306, a determination of a state of an active application is made.At block 1308, in accordance with a determination that the activationduration exceeds the predetermined threshold, and in accordance with adetermination of the state of the active application, the deviceperforms an action. Optionally, at block 1308, in accordance with adetermination that the state of the active application relates touser-to-user voice communication, the device performs the action atleast in part by invoking an application for low-latency asynchronousvoice communication. Optionally, at block 1308, in accordance with adetermination that the state of the active application relates totranscribing a voice input, the device performs the action at least inpart by invoking a dictation application, receiving a voice input, andtranscribing the voice input into a displayed text. Optionally, at block1308, in accordance with a determination that the state of the activeapplication relates to receiving a voice request to execute a task, orin accordance with a determination that the state of the currentapplication does not relate to user-to-user voice communication ortranscribing a voice input, the device performs the action at least inpart by invoking a virtual assistant. Optionally, the device may furtherinclude any of the features described herein in reference to FIGS. 6Aand 6B (e.g., device 600).

Note that details of the processes described above with respect tomethod 1300 (FIG. 13 ) are also applicable in an analogous manner to themethods described below. For example, method 1400 (FIG. 14 ), method1500 (FIG. 15 ), method 1600 (FIG. 16 ), method 1700 (FIG. 17 ), method1800 (FIG. 18 ), method 1900 (FIG. 19 ), and method 2000 (FIG. 20 ) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to method 1300. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 13 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of method1300 (FIG. 13 ), method 1400 (FIG. 14 ), method 1500 (FIG. 15 ), method1600 (FIG. 16 ), method 1700 (FIG. 17 ), method 1800 (FIG. 18 ), method1900 (FIG. 19 ), and method 2000 (FIG. 20 ) may be incorporated with oneanother. Thus, the techniques described with respect to method 1300 maybe relevant to method 1400, method 1500, method 1600, method 1700,method 1800, method 1900, and method 2000.

FIG. 14 is a flow diagram illustrating process 1400 for buttonfunctionalities for user interfaces. In some embodiments, process 1400may be performed at an electronic device with a touch-sensitive displayand a rotatable and depressible input mechanism, such as device 500(FIG. 5 ) or device 700 (FIG. 7 ). Some operations in method 1400 may becombined, the order of some operations may be changed, and someoperations may be omitted.

At block 1402, the device receives data representing an activation ofthe rotatable and depressible input mechanism with an associatedactivation duration. At block 1404, a determination is made as towhether the activation duration exceeds a predetermined threshold. Atblock 1406, in accordance with a determination that the activationduration does not exceed the predetermined threshold, the devicedisplays a first user interface screen including a plurality ofaffordances on the display. At block 1408, while the first userinterface screen is displayed, the device receives second datarepresenting a second activation of the rotatable and depressible inputmechanism with an associated second activation duration. At block 1410,a determination is made as to whether the second activation durationexceeds a second predetermined threshold. At block 1412, in accordancewith a determination that the second activation duration does not exceedthe second predetermined threshold, the device substitutes the firstuser interface screen with a second user interface screen that includesa clock face. Optionally, the device may further include any of thefeatures described herein in reference to FIG. 7 (e.g., device 700).

Note that details of the processes described above with respect tomethod 1400 (FIG. 14 ) are also applicable in an analogous manner to themethods described below. For example, method 1300 (FIG. 13 ), method1500 (FIG. 15 ), method 1600 (FIG. 16 ), method 1700 (FIG. 17 ), method1800 (FIG. 18 ), method 1900 (FIG. 19 ), and method 2000 (FIG. 20 ) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to method 1400. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 14 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of method1300 (FIG. 13 ), method 1400 (FIG. 14 ), method 1500 (FIG. 15 ), method1600 (FIG. 16 ), method 1700 (FIG. 17 ), method 1800 (FIG. 18 ), method1900 (FIG. 19 ), and method 2000 (FIG. 20 ) may be incorporated with oneanother. Thus, the techniques described with respect to method 1400 maybe relevant to method 1300, method 1500, method 1600, method 1700,method 1800, method 1900, and method 2000.

FIG. 15 is a flow diagram illustrating process 1500 for buttonfunctionalities for user interfaces. In some embodiments, process 1500may be performed at an electronic device with a touch-sensitive displayand a rotatable and depressible input mechanism, such as device 500(FIG. 5 ) or device 800 (FIG. 8 ). Some operations in method 1500 may becombined, the order of some operations may be changed, and someoperations may be omitted.

At block 1502, the device receives data representing a first activationof the rotatable and depressible input mechanism and a second activationof the rotatable and depressible input mechanism with an associatedinterval between the first and the second activations. At block 1504, adetermination is made as to whether the interval exceeds a predeterminedthreshold. At block 1506, in accordance with a determination that theinterval does not exceed the predetermined threshold, the device invokesa previously invoked application. Optionally, the device may furtherinclude any of the features described herein in reference to FIG. 8(e.g., device 800).

Note that details of the processes described above with respect tomethod 1500 (FIG. 15 ) are also applicable in an analogous manner to themethods described below. For example, method 1300 (FIG. 13 ), method1400 (FIG. 14 ), method 1600 (FIG. 16 ), method 1700 (FIG. 17 ), method1800 (FIG. 18 ), method 1900 (FIG. 19 ), and method 2000 (FIG. 20 ) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to method 1500. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 15 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of method1300 (FIG. 13 ), method 1400 (FIG. 14 ), method 1500 (FIG. 15 ), method1600 (FIG. 16 ), method 1700 (FIG. 17 ), method 1800 (FIG. 18 ), method1900 (FIG. 19 ), and method 2000 (FIG. 20 ) may be incorporated with oneanother. Thus, the techniques described with respect to method 1500 maybe relevant to method 1300, method 1400, method 1600, method 1700,method 1800, method 1900, and method 2000.

FIG. 16 is a flow diagram illustrating process 1600 for buttonfunctionalities for user interfaces. In some embodiments, process 1600may be performed at an electronic device with a touch-sensitive displaya rotatable and depressible input mechanism, and a button, such asdevice 500 (FIG. 5 ), device 900 (FIG. 9 ), or device 1000 (FIG. 10 ).Some operations in method 1600 may be combined, the order of someoperations may be changed, and some operations may be omitted.

At block 1602, the device receives data representing an activation ofthe button with an associated activation duration. At block 1604, adetermination is made as to whether the activation exceeds apredetermined threshold. At block 1606, in accordance with adetermination that the activation does not exceed the predeterminedthreshold, the device displays a user interface screen including atleast a first affordance indicating a contact from a designated list ofone or more contacts, where the designated list is a subset of a fulllist of contacts on the electronic device. At block 1608, in accordancewith a determination that the activation exceeds the predeterminedthreshold, the device substitutes the user interface screen with asecond user interface screen comprising a second affordance representinga user prompt to power off the electronic device. Optionally, the devicemay further include any of the features described herein in reference toFIGS. 9 and 10 (e.g., device 900 or device 1000).

Note that details of the processes described above with respect tomethod 1600 (FIG. 16 ) are also applicable in an analogous manner to themethods described below. For example, method 1300 (FIG. 13 ), method1400 (FIG. 14 ), method 1500 (FIG. 15 ), method 1700 (FIG. 17 ), method1800 (FIG. 18 ), method 1900 (FIG. 19 ), and method 2000 (FIG. 20 ) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to method 1600. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 16 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of method1300 (FIG. 13 ), method 1400 (FIG. 14 ), method 1500 (FIG. 15 ), method1600 (FIG. 16 ), method 1700 (FIG. 17 ), method 1800 (FIG. 18 ), method1900 (FIG. 19 ), and method 2000 (FIG. 20 ) may be incorporated with oneanother. Thus, the techniques described with respect to method 1600 maybe relevant to method 1300, method 1400, method 1500, method 1700,method 1800, method 1900, and method 2000.

FIG. 17 is a flow diagram illustrating process 1700 for buttonfunctionalities for user interfaces. In some embodiments, process 1700may be performed at an electronic device with a touch-sensitive displaya rotatable and depressible input mechanism, and a button, such asdevice 500 (FIG. 5 ) or device 1100 (FIG. 11 ). Some operations inmethod 1700 may be combined, the order of some operations may bechanged, and some operations may be omitted.

At block 1702, the device receives data representing a first activationof the button and a second activation of the button with an associatedinterval between the first and the second activations. At block 1704, adetermination is made as to whether the interval exceeds a predeterminedthreshold. At block 1706, in accordance with a determination that theinterval does not exceed the predetermined threshold, the device invokesa payments application. Optionally, the device may further include anyof the features described herein in reference to FIG. 11 (e.g., device1100).

Note that details of the processes described above with respect tomethod 1700 (FIG. 17 ) are also applicable in an analogous manner to themethods described below. For example, method 1300 (FIG. 13 ), method1400 (FIG. 14 ), method 1500 (FIG. 15 ), method 1600 (FIG. 16 ), method1800 (FIG. 18 ), method 1900 (FIG. 19 ), and method 2000 (FIG. 20 ) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to method 1700. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 17 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of method1300 (FIG. 13 ), method 1400 (FIG. 14 ), method 1500 (FIG. 15 ), method1600 (FIG. 16 ), method 1700 (FIG. 17 ), method 1800 (FIG. 18 ), method1900 (FIG. 19 ), and method 2000 (FIG. 20 ) may be incorporated with oneanother. Thus, the techniques described with respect to method 1700 maybe relevant to method 1300, method 1400, method 1500, method 1600,method 1800, method 1900, and method 2000.

FIG. 18 is a flow diagram illustrating process 1800 for buttonfunctionalities for user interfaces. In some embodiments, process 1800may be performed at an electronic device with a touch-sensitive displaya rotatable and depressible input mechanism, and a button, such asdevice 500 (FIG. 5 ) or device 1200 (FIG. 12 ). Some operations inmethod 1800 may be combined, the order of some operations may bechanged, and some operations may be omitted.

At block 1802, the device receives data representing an activation ofthe button and an activation of the rotatable and depressible inputmechanism, where the activation of the button and the activation of therotatable and depressible input mechanism are received substantiallysimultaneously. At block 1804, a determination is made as to whether thedata meet predetermined criteria. At block 1806, in accordance with thedetermination that the data meet the predetermined criteria, the deviceis rebooted. Optionally, the device may further include any of thefeatures described herein in reference to FIG. 12 (e.g., device 1200).

Note that details of the processes described above with respect tomethod 1800 (FIG. 18 ) are also applicable in an analogous manner to themethods described below. For example, method 1300 (FIG. 13 ), method1400 (FIG. 14 ), method 1500 (FIG. 15 ), method 1600 (FIG. 16 ), method1700 (FIG. 17 ), method 1900 (FIG. 19 ), and method 2000 (FIG. 20 ) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to method 1800. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 18 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of method1300 (FIG. 13 ), method 1400 (FIG. 14 ), method 1500 (FIG. 15 ), method1600 (FIG. 16 ), method 1700 (FIG. 17 ), method 1800 (FIG. 18 ), method1900 (FIG. 19 ), and method 2000 (FIG. 20 ) may be incorporated with oneanother. Thus, the techniques described with respect to method 1800 maybe relevant to method 1300, method 1400, method 1500, method 1600,method 1700, method 1900, and method 2000.

FIG. 19 is a flow diagram illustrating process 1900 for buttonfunctionalities for user interfaces. In some embodiments, process 1900may be performed at an electronic device with a touch-sensitive displaya rotatable and depressible input mechanism, and a button, such asdevice 500 (FIG. 5 ) or device 1200 (FIG. 12 ). Some operations inmethod 1900 may be combined, the order of some operations may bechanged, and some operations may be omitted.

At block 1902, the device receives data representing an activation ofthe rotatable and depressible input mechanism. At block 1902, adetermination is made as to whether the activation represents a singlepress, a double press, or an extended press of the rotatable anddepressible input mechanism. At block 1906, in accordance with adetermination that the activation represents a single press of therotatable and depressible input mechanism, the device displays a firstuser interface screen including a plurality of affordances on thedisplay. At block 1908, in accordance with a determination that theactivation represents a double press of the rotatable and depressibleinput mechanism, the device invokes a previously invoked application. Atblock 1910, in accordance with a determination that the activationrepresents an extended press of the rotatable and depressible inputmechanism, the device determines a state of an active application. Atblock 1912, in accordance with a determination of the state of theactive application, the device performs an action.

Note that details of the processes described above with respect tomethod 1900 (FIG. 19 ) are also applicable in an analogous manner to themethods described below. For example, method 1300 (FIG. 13 ), method1400 (FIG. 14 ), method 1500 (FIG. 15 ), method 1600 (FIG. 16 ), method1700 (FIG. 17 ), method 1800 (FIG. 18 ), and method 2000 (FIG. 20 ) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to method 1900. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 19 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of method1300 (FIG. 13 ), method 1400 (FIG. 14 ), method 1500 (FIG. 15 ), method1600 (FIG. 16 ), method 1700 (FIG. 17 ), method 1800 (FIG. 18 ), method1900 (FIG. 19 ), and method 2000 (FIG. 20 ) may be incorporated with oneanother. Thus, the techniques described with respect to method 1900 maybe relevant to method 1300, method 1400, method 1500, method 1600,method 1700, method 1800, and method 2000.

FIG. 20 is a flow diagram illustrating process 2000 for buttonfunctionalities for user interfaces. In some embodiments, process 2000may be performed at an electronic device with a touch-sensitive displaya rotatable and depressible input mechanism, and a button, such asdevice 500 (FIG. 5 ) or device 1200 (FIG. 12 ). Some operations inmethod 2000 may be combined, the order of some operations may bechanged, and some operations may be omitted.

At block 2002, the device receives data representing an activation ofthe button. At block 2004, a determination is made as to whether theactivation represents a single press, a double press, or an extendedpress of the button. At block 2006, in accordance with a determinationthat the activation represents a single press of the button, the devicedisplays a first user interface screen including at least a firstaffordance indicating a contact from a designated list of one or morecontacts, where the designated list is a subset of a full list ofcontacts on the electronic device. At block 2008, in accordance with adetermination that the activation represents a double press of thebutton, the device invokes a payments application. At block 2010, inaccordance with a determination that the activation represents anextended press of the button, the device displays a second userinterface screen comprising a second affordance representing a userprompt to power off the electronic device.

Note that details of the processes described above with respect tomethod 12000 (FIG. 20 ) are also applicable in an analogous manner tothe methods described below. For example, method 1300 (FIG. 13 ), method1400 (FIG. 14 ), method 1500 (FIG. 15 ), method 1600 (FIG. 16 ), method1700 (FIG. 17 ), method 1800 (FIG. 18 ), and method 1900 (FIG. 19 ) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to method 2000. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 20 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of method1300 (FIG. 13 ), method 1400 (FIG. 14 ), method 1500 (FIG. 15 ), method1600 (FIG. 16 ), method 1700 (FIG. 17 ), method 1800 (FIG. 18 ), method1900 (FIG. 19 ), and method 2000 (FIG. 20 ) may be incorporated with oneanother. Thus, the techniques described with respect to method 2000 maybe relevant to method 1300, method 1400, method 1500, method 1600,method 1700, method 1800, and method 1900.

In accordance with some embodiments, FIG. 21 shows a functional blockdiagram of an electronic device 2100 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 21 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 21 , an electronic device 2100 includes a display unit2102 configured to display a graphic user interface, a rotatable anddepressible input mechanism unit 2104, and a processing unit 2106coupled to the display unit 2102 and the rotatable and depressible inputmechanism unit 2104. In some embodiments, the processing unit 2106includes a receiving unit 2108, a determining unit 2110, a performingunit 2112, and optionally, a transmitting unit 2114, a display enablingunit 2116, a transcribing unit 2118, an executing unit 2120, and asending unit 2122.

The processing unit 2106 is configured to receive (e.g., with thereceiving unit 2108) data representing an activation of the rotatableand depressible input mechanism unit 2104, the activation having anassociated activation duration; determine (e.g., with the determiningunit 2110) whether the activation duration exceeds a predeterminedthreshold; determine (e.g., with the determining unit 2110) a state ofan active application; and in accordance with a determination that theactivation duration exceeds the predetermined threshold, and inaccordance with a determination of the state of the active application,perform (e.g., with the performing unit 2112) an action.

In some embodiments, the rotatable and depressible input mechanism unit2104 is a mechanical button that is rotatable, and the activationrepresents a depression of the mechanical button.

In some embodiments, the rotatable and depressible input mechanism unit2104 is a capacitive button that is rotatable, and the activationrepresents a touch on the capacitive button.

In some embodiments, the activation does not represent a rotation of therotatable and depressible input mechanism unit 2104.

In some embodiments, in accordance with a determination that the stateof the active application relates to user-to-user voice communication,performing the action comprises invoking an application for low-latencyasynchronous voice communication.

In some embodiments, the processing unit 2106 is further configured to,after invoking the application for low-latency asynchronous voicecommunication, receive (e.g., with the receiving unit 2108) a voiceinput; and transmit (e.g., with the transmitting unit 2114) the voiceinput to a second electronic device capable of receiving the voiceinput.

In some embodiments, in accordance with a determination that the stateof the active application relates to transcribing a voice input,performing the action comprises invoking a dictation application,receiving a voice input, and transcribing the voice input into adisplayed text.

In some embodiments, in accordance with a determination that the stateof the active application relates to receiving a voice request toexecute a task, or in accordance with a determination that the state ofthe current application does not relate to user-to-user voicecommunication or transcribing a voice input, performing the actioncomprises invoking a virtual assistant.

In some embodiments, the processing unit 2106 is further configured to,after invoking the virtual assistant, enable display (e.g., with thedisplay enabling unit 2116) of a user interface screen on the displayunit 2102, the user interface screen including a user prompt for voiceinput.

In some embodiments, the processing unit 2106 is further configured toreceive a voice input.

In some embodiments, the processing unit 2106 is further configured totranscribe (e.g., with the transcribing unit 2118) the voice input intotext and enable display (e.g., with the display enabling unit 2116) ofthe text on the display unit.

In some embodiments, the processing unit 2106 is further configured toenable display (e.g., with the display enabling unit 2116) of a waveformbased on the voice input on the display unit 2102 at a first position.

In some embodiments, the first position is adjacent to the rotatable anddepressible input mechanism unit 2104.

In some embodiments, the processing unit 2106 is further configured todetermine (e.g., with the determining unit 2110) whether the third voiceinput comprises a request to execute a task executable by the virtualassistant and, in accordance with a determination that the third voiceinput comprises a request to execute a task executable by the virtualassistant, execute (e.g., with the executing unit 2120), by the virtualassistant, the task.

In some embodiments, the virtual assistant is run on the electronicdevice.

In some embodiments, the virtual assistant is run on an external devicein wireless communication with the electronic device.

In some embodiments, the processing unit 2106 is further configured tosend (e.g., with the sending unit 2122) first data representing thevoice input to the external device; and receive (e.g., with thereceiving unit 2108), via wireless communication, second data from theexternal device, the second data representing a request to execute atask executable by the virtual assistant; transcribe (e.g., with thetranscribing unit 2118) the request into text; and enable display (e.g.,with the display enabling unit 2116) of the text on the display unit2102.

In some embodiments, the processing unit 2106 is further configured toenable display (e.g., with the display enabling unit 2116) of anaffordance representing a user prompt to display additional data relatedto the request on the external device.

The operations described above with reference to FIG. 13 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 21. For example, receiving operation 1302, determining operations 1304 and1306, and performing operation 1308 are, optionally, implemented byevent sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface (or whether rotation of thedevice) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 22 shows a functional blockdiagram of an electronic device 2200 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 22 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 22 , an electronic device 2200 includes a display unit2202 configured to display a graphic user interface, a rotatable anddepressible input mechanism unit 2204, and a processing unit 2206coupled to the display unit 2202 and the rotatable and depressible inputmechanism unit 2204. In some embodiments, the processing unit 2206includes a receiving unit 2208, a determining unit 2210, a displayenabling unit 2212, and a substitution enabling unit 2214.

The processing unit 2206 is configured to receive (e.g., with thereceiving unit 2208) data representing an activation of the rotatableand depressible input mechanism unit 2204, the activation having anassociated activation duration; determine (e.g., with the determiningunit 2210) whether the activation duration exceeds a predeterminedthreshold; in accordance with a determination that the activationduration does not exceed the predetermined threshold, enable display(e.g., with the display enabling unit 2212) of a first user interfacescreen on the display unit 2202, the first user interface screenincluding a plurality of affordances and the plurality of affordancescomprising an affordance representing an application; while the firstuser interface screen is displayed, receive (e.g., with the receivingunit 2208) second data representing a second activation of the rotatableand depressible input mechanism unit 2204, the second activation havingan associated second activation duration; determine (e.g., with thedetermining unit 2210) whether the second activation duration exceeds asecond predetermined threshold; and, in accordance with a determinationthat the second activation duration does not exceed the secondpredetermined threshold, enable substitution (e.g., with thesubstitution enabling unit 2214) of the display of the first userinterface screen with a display of a second user interface screen, thesecond user interface screen including a clock face.

In some embodiments, the rotatable and depressible input mechanism unit2204 is a mechanical button that is rotatable, and the first and secondactivations both represent a depression of the mechanical button.

In some embodiments, the rotatable and depressible input mechanism unit2204 is a capacitive button that is rotatable, and the first and thesecond activations both represent a touch on the capacitive button.

In some embodiments, the first and the second activations are notrotations of the rotatable and depressible input mechanism unit 2204.

In some embodiments, the clock face includes a user interface objectthat indicates time, and the processing unit 2206 is further configuredto enable display (e.g., with the display enabling unit 2212) of anaffordance on the first user interface screen as part of the pluralityof affordances, where the affordance indicates time, and the affordanceis based on the user interface object.

In some embodiments, the time is current time.

In some embodiments, the user interface object is a representation of ananalog clock comprising an hour hand and a minute hand.

In some embodiments, the affordance is a representation of an analogclock comprising an hour hand and a minute hand.

In some embodiments, the first and second predetermined thresholds arethe same.

In some embodiments, the first activation and the second activation havean associated interval between the first and the second activations andthe interval exceeds a third predetermined threshold.

The operations described above with reference to FIG. 14 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 22. For example, receiving operations 1402 and 1408, determiningoperations 1404 and 1410, displaying operation 1406, and substitutingoperation 1412 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 23 shows a functional blockdiagram of an electronic device 2300 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 23 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 23 , an electronic device 2300 includes a display unit2302 configured to display a graphic user interface, a rotatable anddepressible input mechanism unit 2304, and a processing unit 2306coupled to the display unit 2302 and the rotatable and depressible inputmechanism unit 2304. In some embodiments, the processing unit 2306includes a receiving unit 2308, a determining unit 2310, and an invokingunit 2312.

The processing unit 2306 is configured to receive (e.g., with thereceiving unit 2308) first data representing a first activation of therotatable and depressible input mechanism unit 2304 and a secondactivation of the rotatable and depressible input mechanism unit 2304,the first and the second activations having an associated intervalbetween the first and the second activations; in response to receivingthe first data, determine (e.g., with the determining unit 2310) whetherthe interval between the first and the second activations exceeds apredetermined threshold; and in accordance with a determination that theinterval does not exceed the predetermined threshold, invoke (e.g., withthe invoking unit 2312) a previously invoked application.

In some embodiments, the rotatable and depressible input mechanism unit2304 is a mechanical button that is rotatable, and both of the first andthe second activations represent depressions of the mechanical button.

In some embodiments, the rotatable and depressible input mechanism unit2304 is a capacitive button that is rotatable, and both of the first andthe second activations represent touches on the capacitive button.

In some embodiments, the first and the second activations do notcomprise a rotation of the rotatable and depressible input mechanismunit 2304.

In some embodiments, the previously invoked application is invoked in anapplication start state.

In some embodiments, the previously invoked application is invoked in aprevious state.

In some embodiments, the previous state corresponds to a state of theapplication after a user interaction.

In some embodiments, the previous state corresponds to a stored state ofthe application.

In some embodiments, the previously invoked application is a latestinvoked application that is not currently displayed.

The operations described above with reference to FIG. 15 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 23. For example, receiving operation 1502, determining operation 1504, andinvoking operation 1506 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 24 shows a functional blockdiagram of an electronic device 2400 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 24 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 24 , an electronic device 2400 includes a display unit2402 configured to display a graphic user interface, a touch-sensitivesurface unit 2404 configured to receive contacts, a rotatable anddepressible input mechanism unit 2406, a button unit 2408 and aprocessing unit 2410 coupled to the display unit 2402, thetouch-sensitive surface unit 2404, the rotatable and depressible inputmechanism unit 2406, and the button unit 2408. In some embodiments, theprocessing unit 2410 includes a receiving unit 2412, a determining unit2414, a display enabling unit 2416, and optionally, an invoking unit2418, a providing unit 2420, a sending unit 2422, a substitutionenabling unit 2424, a detecting unit 2426, an executing unit 2428, and apowering unit 2430.

The processing unit 2410 is configured to receive (e.g., with thereceiving unit 2412) first data representing an activation of the buttonunit 2408 the activation having an associated activation duration;determine (e.g., with the determining unit 2414) whether the activationduration exceeds a predetermined threshold; and in accordance with adetermination that the activation duration does not exceed thepredetermined threshold, enable display (e.g., with the display enablingunit 2416) of a user interface screen, the user interface screenincluding at least a first affordance indicating a contact from adesignated list of one or more contacts, where the designated list is asubset of a full list of contacts on the electronic device.

In some embodiments, the button unit 2408 is a mechanical button, andthe activation represents a depression of the mechanical button.

In some embodiments, the button unit 2408 is a capacitive button, andthe activation represents a touch on the capacitive button.

In some embodiments, the designated list of contacts is based on atleast one of the following: time of day of interactions between the userand a contact, frequency of interactions between the user and a contact,and length of interactions between the user and a contact.

In some embodiments, the designated list of contacts is user-designated.

In some embodiments, the processing unit 2410 is further configured to,while the user interface screen is displayed, receive (e.g., with thereceiving unit 2412) second data representing a touch on thetouch-sensitive surface unit 2404 at the location of an affordancecorresponding to a contact; and in response to receiving the seconddata, invoke (e.g., with the invoking unit 2418) a user prompt forselecting an application configured to provide a mode of interactionwith the contact.

In some embodiments, the application is a text messaging application.

In some embodiments, the application is a low-latency asynchronous voicecommunication application.

In some embodiments, the application is an application for sending adrawing to the contact.

In some embodiments, the processing unit 2410 is further configured to,while the user interface screen is displayed, receive (e.g., with thereceiving unit 2412) third data representing a second touch on thetouch-sensitive surface unit 2404 and a third touch on thetouch-sensitive surface unit 2404 separated by an associated durationinterval, where both the second and third touches are at the location ofa portion representing a contact; determine (e.g., with the determiningunit 2414) whether the duration interval is less than a predeterminedduration; and in accordance with a determination that the durationinterval is less than the predetermined duration, provide (e.g., withthe providing unit 2420) an interface, the interface configured toreceive (e.g., with the receiving unit 2412) fourth data representing auser input; and send (e.g., with the sending unit 2422) a signal to asecond electronic device, the signal representing an instructioninstructing the second electronic device to generate a haptic alertbased on the fourth data.

In some embodiments, the user input represented by the fourth datacomprises a touch on the touch-sensitive surface unit 2404.

In some embodiments, the processing unit 2410 is further configured to,in accordance with a determination that the activation duration exceedsthe predetermined threshold, enable substitution (e.g., with thesubstitution enabling unit 2424) of the first user interface screen witha second user interface screen, the second user interface screencomprising a second affordance representing a user prompt to power offthe electronic device.

In some embodiments, the second user interface screen further comprisesa third affordance representing a user prompt to enter a power-savingmode of the electronic device.

In some embodiments, the second user interface screen further comprisesa fourth affordance representing a user prompt to turn off thetouch-sensitive surface unit 2404.

In some embodiments, the touch-sensitive surface unit 2404 is configuredto detect the intensity of touches, and the processing unit 2410 isfurther configured to, while the second user interface screen isdisplayed, detect (e.g., with the detecting unit 2426) a first touch onthe touch-sensitive surface unit 2404, the first touch having a firstcharacteristic intensity; determine (e.g., with the determining unit2414) whether the first characteristic intensity is above an intensitythreshold; and in response to a determination that the firstcharacteristic intensity is above the intensity threshold, execute(e.g., with the executing unit 2428) a separate function of theelectronic device.

In some embodiments, the electronic device is powered off when the firstdata are received, and in accordance with a determination that theactivation duration exceeds the predetermined threshold, the processingunit 2410 further configured to power (e.g., with the powering unit2430) on the electronic device.

The operations described above with reference to FIG. 16 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 24. For example, receiving operation 1602, determining operation 1604,displaying operation 1606, and substituting operation 1608 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 25 shows a functional blockdiagram of an electronic device 2500 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 25 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 25 , an electronic device 2500 includes a display unit2502 configured to display a graphic user interface, a touch-sensitivesurface unit 2504 configured to receive contacts, a rotatable anddepressible input mechanism unit 2506, a button unit 2508 and aprocessing unit 2510 coupled to the display unit 2502, thetouch-sensitive surface unit 2504, the rotatable and depressible inputmechanism unit 2506, and the button unit 2508. In some embodiments, theprocessing unit 2506 includes a receiving unit 2512, a determining unit2514, an invoking unit 2516, and optionally, a display enabling unit2518.

The processing unit 2510 is configured to receive (e.g., with thereceiving unit 2512) first data representing a first activation of thebutton unit 2508 and a second activation of the button unit 2508, thefirst and the second activations having an associated interval betweenthe first and the second activations; determine (e.g., with thedetermining unit 2514) whether the interval between the first and thesecond activations exceeds a predetermined threshold; and in accordancewith a determination that the interval does not exceed the predeterminedthreshold, invoke (e.g., with the invoking unit 2516) a paymentsapplication.

In some embodiments, the button unit 2508 is a mechanical button, andboth of the first and the second activations represent depressions ofthe mechanical button.

In some embodiments, the button unit 2508 is a capacitive button, andboth of the first and the second activations represent touches on thecapacitive button.

In some embodiments, the processing unit 2510 is further configured toenable display (e.g., with the display enabling unit 2518) of a userinterface screen on the display unit 2502, the user interface screenincluding an affordance, the affordance representing a mode of payment.

In some embodiments, the mode of payment is a credit card.

In some embodiments, the affordance comprises a visual representation ofthe face of the credit card, the visual representation indicating acredit card number and a credit card company.

In some embodiments, the mode of payment is a debit card.

In some embodiments, the affordance comprises a visual representation ofthe face of the debit card, the visual representation indicating a debitcard number and a debit card bank.

In some embodiments, the mode of payment is a bank account.

In some embodiments, the affordance indicates at least one of a bankassociated with the bank account, a type of the bank account, and a bankaccount number associated with the bank account.

The operations described above with reference to FIG. 17 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 25. For example, receiving operation 1702, determining operation 1704, andinvoking operation 1706 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 26 shows a functional blockdiagram of an electronic device 2600 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 26 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 26 , an electronic device 2600 includes a display unit2602 configured to display a graphic user interface, a touch-sensitivesurface unit 2604 configured to receive contacts, a rotatable anddepressible input mechanism unit 2606, a button unit 2608 and aprocessing unit 2610 coupled to the display unit 2602, thetouch-sensitive surface unit 2604, the rotatable and depressible inputmechanism unit 2606, and the button unit 2608. In some embodiments, theprocessing unit 2106 includes a receiving unit 2612, a determining unit2614, and a rebooting unit 2616.

The processing unit 2610 is configured to receive (e.g., with thereceiving unit 2612) data representing an activation of the button unit2608 and an activation of the rotatable and depressible input mechanismunit 2606, where the activation of the button unit 2608 has a firstassociated activation duration, the activation of the rotatable anddepressible input mechanism unit 2606 has a second associated activationduration and overlaps with the activation of the button unit 2608 for anoverlap interval, and the activation of the button unit 2608 and theactivation of the rotatable and depressible input mechanism unit 2606are received substantially simultaneously; determine (e.g., with thedetermining unit 2614) whether the data meet predetermined criteria; andin accordance with a determination that the data meet the predeterminedcriteria, reboot (e.g., with the rebooting unit 2616) the electronicdevice.

In some embodiments, the rotatable and depressible input mechanism unit2606 is a mechanical button that is rotatable, and the activation of therotatable and depressible input mechanism unit 2606 comprises adepression of the mechanical button.

In some embodiments, the rotatable and depressible input mechanism unit2606 is a capacitive button that is rotatable, and the activation of therotatable and depressible input mechanism unit 2606 comprises a touch onthe capacitive button.

In some embodiments, the activation of the rotatable and depressibleinput mechanism unit 2606 does not comprise a rotation of the rotatableand depressible input mechanism unit 2606.

In some embodiments, the button unit 2608 is a mechanical button, andthe activation of the button unit 2608 comprises a depression of themechanical button.

In some embodiments, the button unit 2608 is a capacitive button, andthe activation of the button unit 2608 comprises a touch on thecapacitive button.

In some embodiments, the predetermined criteria relate to the first andsecond activation durations, and the processing unit 2610 is furtherconfigured to determine (e.g., with the determining unit 2614) whetherboth the first and the second activation durations exceed apredetermined threshold; and, in accordance with a determination thatboth the first and the second activation durations exceed thepredetermined threshold, reboot (e.g., with the rebooting unit 2616) theelectronic device.

In some embodiments, the predetermined criteria relate to the overlapinterval, and the processing unit 2610 is further configured todetermine (e.g., with the determining unit 2614) whether overlapinterval exceeds a second predetermined threshold, and, in accordancewith a determination that the overlap interval exceeds the secondpredetermined threshold, reboot (e.g., with the rebooting unit 2616) theelectronic device.

The operations described above with reference to FIG. 18 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 26. For example, receiving operation 1802, determining operation 1804, andrebooting operation 1806 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 27 shows a functional blockdiagram of an electronic device 2700 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 27 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 27 an electronic device 2700 includes a display unit2702 configured to display a graphic user interface, a touch-sensitivesurface unit 2704 configured to receive contacts, a rotatable anddepressible input mechanism unit 2706, a button unit 2708 and aprocessing unit 2710 coupled to the display unit 2702, thetouch-sensitive surface unit 2704, the rotatable and depressible inputmechanism unit 2706, and the button unit 2708. In some embodiments, theprocessing unit 2706 includes a receiving unit 2712, a determining unit2714, a display enabling unit 2716, an invoking unit 2718, a performingunit 2720, and optionally, a substitution enabling unit 2722, atransmitting unit 2724, a transcribing unit 2726, an executing unit2728, and a sending unit 2730.

The processing unit 2710 is configured to receive (e.g., with thereceiving unit 2712) first data representing an activation of therotatable and depressible input mechanism unit 2706; determine (e.g.,with the determining unit 2714) whether the activation represents asingle press of the rotatable and depressible input mechanism unit 2706,the single press having an associated press duration, a double press ofthe rotatable and depressible input mechanism unit 2706, the doublepress having an associated interval between a first press of therotatable and depressible input mechanism unit 22706 and a second pressof the rotatable and depressible input mechanism unit 2706, the firstand the second presses of the rotatable and depressible input mechanismunit 2706 each having an associated press duration, or an extended pressof the rotatable and depressible input mechanism unit 2706, the extendedpress having an associated press duration; and, in accordance with adetermination that the activation represents a single press of therotatable and depressible input mechanism unit 2706, enable display(e.g., with the display enabling unit 2716) of a first user interfacescreen on the display unit 2702, the first user interface screenincluding a plurality of affordances, the plurality of affordancescomprising an affordance representing an application; in accordance witha determination that the activation represents a double press of therotatable and depressible input mechanism unit 2706, invoke (e.g., withthe invoking unit 2718) a previously invoked application; and inaccordance with a determination that the activation represents anextended press of the rotatable and depressible input mechanism unit2706, determine (e.g., with the determining unit 2714) a state of anactive application and in accordance with a determination of the stateof the active application, perform (e.g., with the performing unit 2720)an action.

In some embodiments, the processing unit 2710 is further configured toreceive (e.g., with the receiving unit 2712) second data representing anactivation of the button unit 2708; determine (e.g., with thedetermining unit 2714) whether the activation represents a single pressof the button unit 2708, the single press having an associated pressduration, a double press of the button unit 2708, the double presshaving an associated interval between a first press of the button unit2708 and a second press of the button unit 2708, the first and thesecond presses of the button unit 2708 each having an associated pressduration; or an extended press of the button unit 2708, the extendedpress having an associated press duration; and in accordance with adetermination that the activation represents a single press of thebutton unit 2708, enable display (e.g., with the display enabling unit2716) of a third user interface screen, the third user interface screenincluding at least a first affordance indicating a contact from adesignated list of one or more contacts, where the designated list is asubset of a full list of contacts on the electronic device; inaccordance with a determination that the activation represents a doublepress of the button unit 2708, invoke (e.g., with the invoking unit2718) a payments application; and in accordance with a determinationthat the activation represents an extended press of the button unit2708, enable display (e.g., with the display enabling unit 2716) of afourth user interface screen including a second affordance representinga user prompt to power off the electronic device.

In some embodiments, the rotatable and depressible input mechanism unit2706 is a mechanical button that is rotatable, and the single press orthe extended press of the rotatable and depressible input mechanism unit2706 comprises a depression of the mechanical button.

In some embodiments, the rotatable and depressible input mechanism unit2706 is a mechanical button that is rotatable, and the double press ofthe rotatable and depressible input mechanism unit 2706 comprises afirst and a second depression of the mechanical button.

In some embodiments, the rotatable and depressible input mechanism unit2706 is a capacitive button that is rotatable, and the single press orthe extended press of the rotatable and depressible input mechanism unit2706 comprises a touch on the capacitive button.

In some embodiments, the rotatable and depressible input mechanism unit2706 is a capacitive button that is rotatable, and the double press ofthe rotatable and depressible input mechanism unit 2706 comprises afirst and a second touch on the capacitive button.

In some embodiments, the activation does not comprise a rotation of therotatable and depressible input mechanism unit 2706.

In some embodiments, the button unit 2708 is a mechanical button, andthe single press or the extended press of the button unit 2708 comprisesa depression of the mechanical button.

In some embodiments, the button unit 2708 is a mechanical button, andthe double press of the button unit 2708 comprises a first and a seconddepression of the mechanical button.

In some embodiments, the button unit 2708 is a capacitive button, andthe single press or the extended press of the button unit 2708 comprisesa touch on the capacitive button.

In some embodiments, the button unit 2708 is a capacitive button, andthe double press of the button unit 2708 comprises a first and a secondtouch on the capacitive button.

In some embodiments, determining whether the activation represents asingle press of the rotatable and depressible input mechanism unit 2706comprises determining whether the press duration of the single pressexceeds a first predetermined threshold; and, in accordance with adetermination that the press duration of the single press does notexceed the first predetermined threshold, determining whether third datais received within a second interval after receiving the first data, thethird data representing an activation of the rotatable and depressibleinput mechanism unit 2706; and in accordance with a determination thatthe third data is not received within the second interval, determiningthat the activation represents a single press of the rotatable anddepressible input mechanism unit 2706.

In some embodiments, the processing unit 2710 is further configured to,in accordance with the determination that the activation represents asingle press of the rotatable and depressible input mechanism unit 2706,and while the first user interface screen is displayed, receive (e.g.,with the receiving unit 2712) fourth data representing a second singlepress of the rotatable and depressible input mechanism unit 2706; and inresponse to receiving the fourth data, enable substitution (e.g., withthe substitution enabling unit 2722) of the display of the first userinterface screen with a display of a fifth user interface screen, thefifth user interface screen including a clock face.

In some embodiments, the clock face includes a first user interfaceobject that indicates time, and the processing unit 2710 is furtherconfigured to enable display (e.g., with the display enabling unit 2716)of a third affordance on the fifth user interface screen as part of theplurality of affordances, where the third affordance indicates the time,and the third affordance is based on the first user interface object.

In some embodiments, the time is current time.

In some embodiments, the first user interface object is a representationof an analog clock comprising an hour hand and a minute hand.

In some embodiments, the third affordance is a representation of ananalog clock including an hour hand and a minute hand.

In some embodiments, determining whether the activation represents adouble press of the rotatable and depressible input mechanism unit 2706comprises determining whether the press duration of the first press ofthe double press exceeds a second predetermined threshold; in accordancewith a determination that the press duration of the first press of thedouble press does not exceed the second predetermined threshold,determining whether the interval between the first press of the doublepress and the second press of the double press exceeds a thirdpredetermined threshold; in accordance with a determination that theinterval between the first press of the double press and the secondpress of the double press does not exceed the third predeterminedthreshold, determining whether the press duration of the second press ofthe double press exceeds a fourth predetermined threshold; and inaccordance with a determination that the press duration of the secondpress of the double press does not exceed the second predeterminedthreshold, determining that the activation represents a double press ofthe rotatable and depressible input mechanism unit 2706.

In some embodiments, the second and the fourth predetermined thresholdsare the same.

In some embodiments, in accordance with the determination that theactivation represents a double press of the rotatable and depressibleinput mechanism unit 2706, the previously invoked application is invokedin an application start state.

In some embodiments, in accordance with the determination that theactivation represents a double press of the rotatable and depressibleinput mechanism unit 2706, the previously invoked application is invokedin a previous state.

In some embodiments, in accordance with the determination that theactivation represents a double press of the rotatable and depressibleinput mechanism unit 2706, the previous state corresponds to a state ofthe application after a user interaction.

In some embodiments, in accordance with the determination that theactivation represents a double press of the rotatable and depressibleinput mechanism unit 2706, the previous state corresponds to a storedstate of the application.

In some embodiments, the previously invoked application is a latestinvoked application that is not currently displayed.

In some embodiments, determining whether the activation represents anextended press of the rotatable and depressible input mechanism unit2706 comprises determining whether the press duration of the extendedpress exceeds a fifth predetermined threshold; and, in accordance with adetermination that the press duration of the extended press exceeds thefifth predetermined threshold, determining that the activationrepresents an extended press of the rotatable and depressible inputmechanism unit 2706.

In some embodiments, in accordance with the determination that theactivation represents an extended press of the rotatable and depressibleinput mechanism unit 2706, and in accordance with a determination thatthe state of the active application relates to user-to-user voicecommunication, performing the action comprises invoking an applicationfor low-latency asynchronous voice communication.

In some embodiments, the processing unit 2710 is further configured to,after invoking the application for low-latency asynchronous voicecommunication, receive (e.g., with the receiving unit 2712) a secondvoice input and transmit (e.g., with the transmitting unit 2724) thesecond voice input to a second electronic device capable of receivingthe second voice input.

In some embodiments, in accordance with the determination that theactivation represents an extended press of the rotatable and depressibleinput mechanism unit 2706, and in accordance with a determination thatthe state of the active application relates to transcribing a voiceinput, performing the action comprises invoking a dictation application;receiving a voice input; and transcribing the voice input into adisplayed text.

In some embodiments, in accordance with the determination that theactivation represents an extended press of the rotatable and depressibleinput mechanism unit 2706; and, in accordance with a determination thatthe state of the active application relates to receiving a voice requestto execute a task, or in accordance with a determination that the stateof the current application does not relate to user-to-user voicecommunication or transcribing a voice input, performing the actioncomprises invoking a virtual assistant.

In some embodiments, the processing unit 2710 is further configured to,after invoking the virtual assistant, enable display (e.g., with thedisplay enabling unit 2716) of a sixth user interface screen on thedisplay unit 2702, the sixth user interface screen including a userprompt for voice input.

In some embodiments, the processing unit 2710 is further configured toreceive (e.g., with the receiving unit 2712) a voice input.

In some embodiments, the processing unit 2710 is further configured totranscribe (e.g., with the transcribing unit 2726) the voice input intotext and enable display (e.g., with the display enabling unit 2716) ofthe text on the display unit 2702.

In some embodiments, the processing unit 2710 is further configured toenable display (e.g., with the display enabling unit 2716) of a waveformbased on the voice input on the display unit 2702 at a first position.

In some embodiments, the first position is adjacent to the rotatable anddepressible input mechanism unit 2706.

In some embodiments, the processing unit 2710 is further configured todetermine (e.g., with the determining unit 2714) whether the voice inputcomprises a request to execute a task executable by the virtualassistant and, in accordance with a determination that the voice inputcomprises a request to execute a task executable by the virtualassistant, execute (e.g., with the executing unit 2728), by the virtualassistant, the task.

In some embodiments, the virtual assistant is run on the electronicdevice.

In some embodiments, the virtual assistant is run on an external devicein wireless communication with the electronic device.

In some embodiments, the processing unit 2710 is further configured tosend (e.g., with the sending unit 2730) fifth data representing thevoice input to the external device; receive (e.g., with the receivingunit 2712), via wireless communication, sixth data from the externaldevice, the sixth data representing a request to execute a taskexecutable by the virtual assistant; transcribe (e.g., with thetranscribing unit 2726) the request into text; and enable display (e.g.,with the display enabling unit 2716) of the text on the display unit2702.

In some embodiments, the processing unit 2710 is further configured toenable display (e.g., with the display enabling unit 2716) of a fourthaffordance representing a user prompt to display additional data relatedto the request on the external device.

The operations described above with reference to FIG. 19 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 27. For example, receiving operation 1902, determining operations 1904 and1910, displaying operation 1906, invoking operation 1908, and performingoperation 1912 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 28 shows a functional blockdiagram of an electronic device 2800 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 28 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 28 , an electronic device 2800 includes a display unit2802 configured to display a graphic user interface, a touch-sensitivesurface unit 2804 configured to receive contacts, a rotatable anddepressible input mechanism unit 2806, a button unit 2808 and aprocessing unit 2810 coupled to the display unit 2802, thetouch-sensitive surface unit 2804, the rotatable and depressible inputmechanism unit 2806, and the button unit 2808. In some embodiments, theprocessing unit 2806 includes a receiving unit 2812, a determining unit2814, a display enabling unit 2816, an invoking unit 2818, andoptionally, a performing unit 2820, a detecting unit 2822, an executingunit 2824, and a sending unit 2826.

The processing unit 2810 is configured to receive (e.g., with thereceiving unit 2812) first data representing an activation of the buttonunit 2808; determine (e.g., with the determining unit 2814) whether theactivation represents a single press of the button unit 2808, the singlepress having an associated press duration, a double press of the buttonunit 2808, the double press having an associated interval between afirst consecutive press and a second consecutive press, the first andsecond consecutive presses each having an associated press duration, oran extended press of the button unit 2808, the extended press having anassociated press duration; and in accordance with a determination thatthe activation represents a single press of the button unit 2808, enabledisplay (e.g., with the display enabling unit 2816) of a first userinterface screen, the first user interface screen including at least afirst affordance indicating a contact from a designated list of one ormore contacts, where the designated list is a subset of a full list ofcontacts on the electronic device; in accordance with a determinationthat the activation represents a double press of the button unit 2808,invoke (e.g., with the invoking unit 2818) a payments application; andin accordance with a determination that the activation represents anextended press of the button unit 2808, enable display (e.g., with thedisplay enabling unit 2816) of a second user interface screen, thesecond user interface screen comprising a second affordance representinga user prompt to power off the electronic device.

In some embodiments, the processing unit 2810 is further configured toreceive (e.g., with the receiving unit 2812) second data representing anactivation of the rotatable and depressible input mechanism unit 2806;determine (e.g., with the determining unit 2814) whether the activationrepresents a single press of the rotatable and depressible inputmechanism unit 2806, the single press having an associated pressduration, a double press of the rotatable and depressible inputmechanism unit 2806, the double press having an associated intervalbetween a first consecutive press and a second consecutive press, thefirst and second consecutive presses each having an associated pressduration, or an extended press of the rotatable and depressible inputmechanism unit 2806, the extended press having an associated pressduration; and in accordance with a determination that the activationrepresents a single press of the rotatable and depressible inputmechanism unit 2806, enable display (e.g., with the display enablingunit 2816) of a third user interface screen on the display unit 2802,the third user interface screen including a plurality of affordances,the plurality of affordances comprising an affordance representing anapplication; in accordance with a determination that the activationrepresents a double press of the rotatable and depressible inputmechanism unit 2806, invoke (e.g., with the invoking unit 2818) apreviously invoked application; and in accordance with a determinationthat the activation represents an extended press of the rotatable anddepressible input mechanism unit 2806, determine (e.g., with thedetermining unit 2814) a state of an active application; and inaccordance with a determination of the state of the active application,perform (e.g., with the performing unit 2820) an action.

In some embodiments, the button unit 2808 is a mechanical button, andthe single press or the extended press of the button unit 2808 comprisesa depression of the mechanical button.

In some embodiments, the button unit 2808 is a mechanical button, andthe double press of the button unit 2808 comprises a first and a seconddepression of the mechanical button.

In some embodiments, the button unit 2808 is a capacitive button, andthe single press or the extended press of the button unit 2808 comprisesa touch on the capacitive button.

In some embodiments, the button unit 2808 is a capacitive button, andthe double press of the button unit 2808 comprises a first and a secondtouch on the capacitive button.

In some embodiments, the rotatable and depressible input mechanism unit2806 is a mechanical button that is rotatable, and the single press orthe extended press of the rotatable and depressible input mechanism unit2806 comprises a depression of the mechanical button.

In some embodiments, the rotatable and depressible input mechanism unit2806 is a mechanical button that is rotatable, and the double press ofthe rotatable and depressible input mechanism unit 2806 comprises afirst and a second depression of the mechanical button.

In some embodiments, the rotatable and depressible input mechanism unit2806 is a capacitive button that is rotatable, and the single press orthe extended press of the rotatable and depressible input mechanism unit2806 comprises a touch on the capacitive button.

In some embodiments, the rotatable and depressible input mechanism unit2806 is a capacitive button that is rotatable, and the double press ofthe rotatable and depressible input mechanism unit 2806 comprises afirst and a second touches on the capacitive button.

In some embodiments, the activation does not comprise a rotation of therotatable and depressible input mechanism unit 2806.

In some embodiments, determining whether the activation represents adouble press of the button unit 2808 comprises determining whether thepress duration of the first press of the double press exceeds a firstpredetermined threshold; in accordance with a determination that thepress duration of the first press of the double press does not exceedthe first predetermined threshold, determining whether the intervalbetween the first press of the double press and the second press of thedouble press exceeds a second predetermined threshold; in accordancewith a determination that the interval between the first press of thedouble press and the second press of the double press does not exceedthe second predetermined threshold, determining whether the pressduration of the second press of the double press exceeds a thirdpredetermined threshold; and in accordance with a determination that thepress duration of the second press of the double press does not exceedthe third predetermined threshold, determining that the activationrepresents a double press of the button unit 2808.

In some embodiments, the first and the third predetermined thresholdsare the same.

In some embodiments, the processing unit 2810 is further configured to,in accordance with the determination that the activation represents adouble press of the button unit 2808, and after invoking the paymentsapplication, enable display (e.g., with the display enabling unit 2816)of a fifth user interface screen on the display unit 2802, the fifthuser interface screen including a fifth affordance, the fifth affordancerepresenting a mode of payment.

In some embodiments, the mode of payment is a credit card.

In some embodiments, the fifth affordance comprises a visualrepresentation of the face of the credit card, the visual representationindicating a credit card number and a credit card company.

In some embodiments, the mode of payment is a debit card.

In some embodiments, the fifth affordance comprises a visualrepresentation of the face of the debit card, the visual representationindicating a debit card number and a debit card bank.

In some embodiments, the mode of payment is a bank account.

In some embodiments, the fifth affordance indicates at least one of abank associated with the bank account, a type of the bank account, and abank account number associated with the bank account.

In some embodiments, determining whether the activation represents anextended press of the button unit 2808 comprises determining whether thepress duration of the extended press exceeds a fourth predeterminedthreshold; and, in accordance with a determination that the pressduration of the extended press exceeds the fourth predeterminedthreshold, determining that the activation represents an extended pressof the button unit 2808.

In some embodiments, the processing unit 2810 is further configured toenable display (e.g., with the display enabling unit 2816) of a sixthuser interface screen comprising a sixth affordance representing a userprompt to power off the electronic device.

In some embodiments, the sixth user interface screen further comprises aseventh affordance representing a user prompt to enter a power-savingmode of the electronic device.

In some embodiments, the sixth user interface screen further comprisesan eighth affordance representing a user prompt to turn off thetouch-sensitive surface unit.

In some embodiments, the touch-sensitive surface unit is configured todetect the intensity of touches, and the processing unit 2810 is furtherconfigured to, while the sixth user interface screen is displayed,detect (e.g., with the detecting unit 2822) a first touch on thetouch-sensitive surface unit, the first contact having a firstcharacteristic intensity; determine (e.g., with the determining unit2814) whether the first characteristic intensity is above an intensitythreshold; and in response to a determination that the firstcharacteristic intensity is above the intensity threshold, execute(e.g., with the executing unit 2824) a separate function of theelectronic device.

In some embodiments, in accordance with a determination that theactivation represents an extended press of the button unit 2808, wherethe electronic device is powered off when the first data are received,and the processing unit 2810 is further configured to power on theelectronic device.

In some embodiments, determining whether the activation represents asingle press of the button unit 2808 comprises determining whether thepress duration of the single press exceeds a fifth predeterminedthreshold; and in accordance with a determination that the pressduration of the single press does not exceed the fifth predeterminedthreshold, determining whether second data is received within a secondinterval after receiving the first data, the second data representing anactivation of the button unit 2808; and in accordance with adetermination that the second data is not received within the secondinterval, determining that the activation represents a single press ofthe button unit 2808.

In some embodiments, the processing unit 2810 is further configured to,in accordance with the determination that the activation represents asingle press of the button unit 2808, and while the first user interfacescreen is displayed, automatically compile the designated list ofcontacts based on at least one of the following: time of day ofinteractions between a user and a contact, frequency of interactionsbetween a user and a contact, and length of interactions between a userand a contact.

In some embodiments, the designated list of contacts is user-designated.

In some embodiments, the processing unit 2810 is further configured to,while the first user interface screen is displayed, receive third datarepresenting a touch on the touch-sensitive surface unit at the locationof a first affordance indicating a contact; and in response to receivingthe third data, invoke (e.g., with the invoking unit 2818) a user promptfor selecting an application configured to provide a mode of interactionwith the indicated contact.

In some embodiments, the application is a text messaging application.

In some embodiments, the application is a low-latency asynchronous voicecommunication application.

In some embodiments, the application is an application for sending adrawing to the indicated contact.

In some embodiments, the processing unit 2810 is further configured to,in accordance with the determination that the activation represents asingle press of the button unit 2808, and while the first user interfacescreen is displayed receive (e.g., with the receiving unit 2812) fourthdata representing a second touch on the touch-sensitive surface unit anda third touch on the touch-sensitive surface unit separated by anassociated duration interval, where both the second and third touchesare at the location of a portion representing a contact; determine(e.g., with the determining unit 2814) whether the duration interval isless than a sixth predetermined duration; and in accordance with adetermination that the duration interval is less than the sixthpredetermined duration, provide an interface, the interface configuredto receive (e.g., with the receiving unit 2812) fifth data representinga user input and send (e.g., with the sending unit 2826) a signal to asecond electronic device, the signal representing an instructioninstructing the second electronic device to generate a haptic alertbased on the fifth data.

In some embodiments, the user input represented by the fifth datacomprises a touch on the touch-sensitive surface unit.

The operations described above with reference to FIG. 20 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 2. For example, receiving operation 2002, determining operation 2004,displaying operations 2004 and 2010, and invoking operation 2008 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface (or whether rotationof the device) corresponds to a predefined event or sub-event, such asselection of an object on a user interface, or rotation of the devicefrom one orientation to another. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally uses or calls data updater 176 or object updater177 to update the application internal state 192. In some embodiments,event handler 190 accesses a respective GUI updater 178 to update whatis displayed by the application. Similarly, it would be clear to aperson having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

What is claimed is:
 1. An electronic device, comprising: atouch-sensitive display; a button; a rotatable and depressible inputmechanism; one or more processors; memory; and one or more programs,wherein the one or more programs are stored in the memory and configuredto be executed by the one or more processors, the one or more programsincluding instructions for: receiving first data representing a firstactivation of the button and a second activation of the button of thebutton, the first and the second activations having an associatedinterval between the first and the second activations; determiningwhether the interval between the first and the second activationsexceeds a predetermined threshold; and in accordance with adetermination that the interval does not exceed the predeterminedthreshold: displaying, on the touch-sensitive display, a user interfacecorresponding to a payments application.
 2. The electronic device ofclaim 1, wherein the button is a mechanical button, and wherein both ofthe first and the second activations represent depressions of themechanical button.
 3. The electronic device of claim 1, wherein thebutton is a capacitive button, and wherein both of the first and thesecond activations represent touches on the capacitive button.
 4. Theelectronic device of claim 1, wherein the user interface includes anaffordance, the affordance representing a mode of payment.
 5. Theelectronic device of claim 4, wherein the mode of payment is a creditcard.
 6. The electronic device of claim 5, wherein the affordancecomprises a visual representation of the face of the credit card, thevisual representation indicating a credit card number and a credit cardcompany.
 7. The electronic device of claim 4, wherein the mode ofpayment is a debit card.
 8. The electronic device of claim 7, whereinthe affordance comprises a visual representation of the face of thedebit card, the visual representation indicating a debit card number anda debit card bank.
 9. The electronic device of claim 4, wherein the modeof payment is a bank account.
 10. The electronic device of claim 9,wherein the affordance indicates at least one of a bank associated withthe bank account, a type of the bank account, and a bank account numberassociated with the bank account.
 11. A non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of an electronic device with a touch-sensitivedisplay, a button, and a rotatable and depressible input mechanism, theone or more programs including instructions for: receiving first datarepresenting a first activation of the button and a second activation ofthe button of the button, the first and the second activations having anassociated interval between the first and the second activations;determining whether the interval between the first and the secondactivations exceeds a predetermined threshold; and in accordance with adetermination that the interval does not exceed the predeterminedthreshold: displaying, on the touch-sensitive display, a user interfacecorresponding to a payments application.
 12. The non-transitorycomputer-readable storage medium of claim 11, wherein the button is amechanical button, and wherein both of the first and the secondactivations represent depressions of the mechanical button.
 13. Thenon-transitory computer-readable storage medium of claim 11, wherein thebutton is a capacitive button, and wherein both of the first and thesecond activations represent touches on the capacitive button.
 14. Thenon-transitory computer-readable storage medium of claim 11, wherein theuser interface includes an affordance, the affordance representing amode of payment.
 15. The non-transitory computer-readable storage mediumof claim 14, wherein the mode of payment is a credit card.
 16. Thenon-transitory computer-readable storage medium of claim 15, wherein theaffordance comprises a visual representation of the face of the creditcard, the visual representation indicating a credit card number and acredit card company.
 17. The non-transitory computer-readable storagemedium of claim 14, wherein the mode of payment is a debit card.
 18. Thenon-transitory computer-readable storage medium of claim 17, wherein theaffordance comprises a visual representation of the face of the debitcard, the visual representation indicating a debit card number and adebit card bank.
 19. The non-transitory computer-readable storage mediumof claim 14, wherein the mode of payment is a bank account.
 20. Thenon-transitory computer-readable storage medium of claim 19, wherein theaffordance indicates at least one of a bank associated with the bankaccount, a type of the bank account, and a bank account numberassociated with the bank account.
 21. A method, comprising: at anelectronic device with a touch-sensitive display, a button, and arotatable and depressible input mechanism: receiving first datarepresenting a first activation of the button and a second activation ofthe button of the button, the first and the second activations having anassociated interval between the first and the second activations;determining whether the interval between the first and the secondactivations exceeds a predetermined threshold; and in accordance with adetermination that the interval does not exceed the predeterminedthreshold: displaying, on the touch-sensitive display, a user interfacecorresponding to a payments application.
 22. The method of claim 21,wherein the button is a mechanical button, and wherein both of the firstand the second activations represent depressions of the mechanicalbutton.
 23. The method of claim 21, wherein the button is a capacitivebutton, and wherein both of the first and the second activationsrepresent touches on the capacitive button.
 24. The method of claim 21,wherein the user interface includes an affordance, the affordancerepresenting a mode of payment.
 25. The method of claim 24, wherein themode of payment is a credit card.
 26. The method of claim 25, whereinthe affordance comprises a visual representation of the face of thecredit card, the visual representation indicating a credit card numberand a credit card company.
 27. The method of claim 24, wherein the modeof payment is a debit card.
 28. The method of claim 27, wherein theaffordance comprises a visual representation of the face of the debitcard, the visual representation indicating a debit card number and adebit card bank.
 29. The method of claim 24, wherein the mode of paymentis a bank account.
 30. The method of claim 29, wherein the affordanceindicates at least one of a bank associated with the bank account, atype of the bank account, and a bank account number associated with thebank account.